# CVE-2026-129217: bgpd: out-of-bounds heap read and crash on NOTIFICATION Cease/Hard Reset with one data byte


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129217, GHSA-hgq9-rmfx-r8g6, UBUNTU-CVE-2026-129217

## What is CVE-2026-129217?

CVE-2026-129217 is a medium-severity vulnerability in FRRouting, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-191 (Integer Underflow (Wrap or Wraparound)), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-129217?


## How do I fix CVE-2026-129217?

Upgrade to a fixed version.

## Is CVE-2026-129217 being exploited?

There is no known exploitation of CVE-2026-129217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129217 and fix it if it is affected.

What it is: CVE-2026-129217 is a medium-severity vulnerability in FRRouting, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129217 in the wild and no public exploit code.

Affected product: FRRouting. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129217/ (Markdown: https://insights.sbomify.com/CVE-2026-129217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129217
- OSV: https://osv.dev/vulnerability/CVE-2026-129217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129217/
Summaries are generated and may contain mistakes; the official description above is the record.
