CVE-2026-129217

MEDIUMPre-NVD 6.06.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-125721 (ENISA EUVD) · GHSA-hgq9-rmfx-r8g6 (GitHub Security Advisories)Source: ENISA EUVD

6.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.0Exploit: None knownExposed services: Not assessed

The CVE record names the fixed release — apply it.

In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end of a heap buffer and the 16-bit length of the encapsulated data underflows to 65535, causing a 65535-byte out-of-bounds heap read followed by an assertion failure. A remote BGP peer that has established a session and negotiated the Graceful Restart capability with the Notification (N) bit can send such a message to crash the bgpd daemon, terminating all BGP sessions (denial of service). This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0.

CVSS
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity60% × 45%
Impact severity (EG Severity): CVSS 6.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.0): severity, escalated by confirmed exploitation. This CVE's 6.0 is its impact severity (EG Severity), not escalated.

EG Severity
6.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 13, 2026

Last Modified

November 17, 2026

Advisory Details (2)

Auto-updated Nov 13, 2026
Fix named in the CVE record. Sources: github_pr.
GitHub pull request

bgpd: validate incoming NOTIFICATION messages

Fix merged in FRRouting/frr PR #20796 on 2026-02-13 — awaiting tagged release

https://github.com/FRRouting/frr/pull/20796
Web page

Heap-over-flow in bgpd v10.7.0 · Issue #20793 · FRRouting/frr · GitHub

https://github.com/FRRouting/frr/issues/20793

Vendor Advisories for CVE-2026-129217(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-20 05:42 UTCEchelonGraph re-scored
  4. 2026-11-20 05:42 UTCGHSA enrichmentGHSA-hgq9-rmfx-r8g6 · GitHub severity MODERATE
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-17 22:33 UTCEchelonGraph re-scored
  8. 2026-11-17 22:33 UTCGHSA enrichmentGHSA-hgq9-rmfx-r8g6 · GitHub severity MODERATE
  9. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-17 00:28 UTCEchelonGraph re-scored
  11. 2026-11-17 00:28 UTCGHSA enrichmentGHSA-hgq9-rmfx-r8g6 · GitHub severity MODERATE
  12. 2026-11-16 23:42 UTCEchelonGraph re-scored
  13. 2026-11-16 23:42 UTCGHSA enrichmentGHSA-hgq9-rmfx-r8g6 · GitHub severity MODERATE
  14. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  15. 2026-11-15 16:57 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-11-14 03:00 UTCEchelonGraph re-scored
  18. 2026-11-14 03:00 UTCGHSA enrichmentGHSA-hgq9-rmfx-r8g6 · GitHub severity MODERATE
  19. 2026-11-13 20:01 UTCENISA EUVD ID recordedEUVD-2026-125721 · Source: ENISA EUVD
  20. 2026-11-13 19:21 UTCEchelonGraph re-scoredFirst assessed: 6.0 MEDIUM
  21. 2026-11-13 19:11 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129217?
CVE-2026-129217 is a medium-severity vulnerability; its CVE record was published on November 13, 2026. In FRRouting (FRR) 8.3 through 10.5.1, bgp_notify_decapsulate_hard_reset() in bgpd/bgp_packet.c does not validate the length of the data field of a received BGP NOTIFICATION Cease/Hard Reset message (RFC 8538). When the data field is exactly one byte long, the function reads one byte past the end…
When was the CVE record for CVE-2026-129217 published?
The CVE record for CVE-2026-129217 was published on November 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 17, 2026; the record at its source may have been updated since.
Is CVE-2026-129217 actively exploited?
CVE-2026-129217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129217?
CVE-2026-129217 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129217?
The CVE record for CVE-2026-129217 names the fix: "This is fixed in 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 and 10.6.0." The vendor advisories EchelonGraph has for CVE-2026-129217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129217?

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