PLATEAUMinimal movement since 2022-02-04, 1675 days at 0.03, as of 2026-09-06. arc-rules@v1
Foresight · where to check next
This record is one instance of CWE-399. The index holds 2695 prior instances of this class, 11 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1
Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is
Which product do you run? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
Published consequencesMITRE publishes no common consequences for this weakness.cwe-consequences@4.20
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Fixed inNo fix version in held sources, as the index stood on 6 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline
CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$98,100over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate
$98,100 = $4.99M incident cost x 0.6121449559255632 exposure x 0.03213 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
What it is stated by the CNA
Cisco IOS 12.4 and 15.0 through 15.6 and IOS XE 3.1 through 3.18 and 16.1 allow remote attackers to cause a denial of service (memory consumption or device reload) via fragmented IKEv1 packets, aka Bug ID CSCuy47382. receipt
NVD's analysis a second authority
severity
7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
weakness
CWE-399
affected versions
cisco ios 12.4\(15\)t7; cisco ios 12.4\(15\)t8; cisco ios 12.4\(15\)t9; and 398 more, listed in full below
13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
The record had been public for 9 years, 11 months when this index was last written.
Published 2016-10-05 receipt · Index as of 2026-09-06 derived
The pattern, elsewhere
This record is one instance of CWE-399. The index holds 2695 prior instances of this class, 11 KEV-listed. The nearest of its KEV-listed records are drawn beside this. cwe-consequences@4.20
CVE-2018-0154 · Cisco IOSmatches 8 of 8KEV listed · 2018receipt
CVE-2018-0156 · Cisco IOS and IOS XEmatches 8 of 8KEV listed · 2018receipt
CVE-2017-12231 · Cisco IOSmatches 8 of 8KEV listed · 2017receipt
CVE-2017-12237 · Cisco IOS and IOS XEmatches 8 of 8KEV listed · 2017receipt
CVE-2017-6627 · Cisco IOS and Cisco IOS XEmatches 8 of 8KEV listed · 2017receipt
CVE-2018-0179 · Cisco IOSmatches 7 of 8KEV listed · 2018receipt
"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1
2695 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.
No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.