CVE-2026-102714

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (3rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

_nx_icmpv6_validate_options() scans the option area with while (length > 2) (common/src/nx_icmpv6_validate_options.c:79). An area whose size leaves a one- or two-byte residue exits the loop with that tail unexamined; the residue is not negative, so the function returns NX_SUCCESS. Its zero-length rejection never sees those bytes.

Every consumer then re-walks the same area, reading a two-byte option header at the residue and subtracting nx_icmpv6_option_length << 3 with no zero check and no remaining-length check. Three outcomes follow, selected by bytes the attacker controls.

Zero length byte. The walker subtracts zero and advances zero. All four handlers loop forever — _nx_icmpv6_process_ra (nx_icmpv6_process_ra.c:245, :528), _nx_icmpv6_process_ns (:251, :329), _nx_icmpv6_process_na (:147, :156) and _nx_icmpv6_process_redirect (:247, :350). The walk runs in the IP thread, which is the highest-priority thread and does not yield inside the loop, so the system stops until a watchdog reset and the frame can be replayed after each one.

Non-zero length byte on a short residue. The three unsigned counters underflow — 2 - 8 becomes 0xFFFFFFFA — and the walk continues past the packet buffer, reading until it faults or meets a zero length byte and freezes. The Router Advertisement counter is signed and exits cleanly in this case.

One-byte residue. The walker reads a two-byte option header, over-reading one byte.

During a runaway walk, stray bytes parsing as a link-layer address option are copied into the neighbor cache (nx_icmpv6_process_ns.c:280, :293) and subsequently used as the destination MAC for frames to that neighbour, placing off-packet memory on the link. Confirmed by inspection, not reproduced.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Vendor Advisories for CVE-2026-102714(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 04:23 UTCGHSA enrichment
  2. 2026-10-03 15:20 UTCEG score recompute
  3. 2026-10-03 15:19 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 02:12 UTCEG score recompute
  6. 2026-10-03 02:12 UTCGHSA enrichment
  7. 2026-10-02 13:08 UTCGHSA enrichment
  8. 2026-10-02 00:01 UTCEG score recompute
  9. 2026-10-02 00:01 UTCGHSA enrichment
  10. 2026-10-01 19:49 UTCEPSS rescore
  11. 2026-10-01 10:40 UTCGHSA enrichment
  12. 2026-09-30 21:34 UTCEG score recompute
  13. 2026-09-30 21:34 UTCGHSA enrichment
  14. 2026-09-30 15:02 UTCEPSS rescore
  15. 2026-09-30 08:24 UTCGHSA enrichment
  16. 2026-09-29 19:21 UTCGHSA enrichment
  17. 2026-09-29 19:11 UTCEG score recompute
  18. 2026-09-29 19:10 UTCGHSA enrichment
  19. 2026-09-29 18:51 UTCEG score recompute
  20. 2026-09-29 18:51 UTCGHSA enrichment
  21. 2026-09-29 18:27 UTCEG score recompute
  22. 2026-09-29 17:49 UTCEG score recompute
  23. 2026-09-29 17:48 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102714?
CVE-2026-102714 is a high vulnerability published on September 29, 2026. nxicmpv6validateoptions() scans the option area with while (length > 2) (common/src/nxicmpv6validateoptions.c:79). An area whose size leaves a one- or two-byte residue exits the loop with that tail unexamined; the residue is not negative, so the function returns NXSUCCESS. Its zero-length rejection…
When was CVE-2026-102714 disclosed?
CVE-2026-102714 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102714 actively exploited?
CVE-2026-102714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102714?
CVE-2026-102714 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102714?
No fix for CVE-2026-102714 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-102714 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-102714

Explore →

Is Your Infrastructure Affected by CVE-2026-102714?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.