bgpd out-of-bounds heap read and crash on one-byte Cease/Hard Reset message
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- Low · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
FRRouting versions 8.3 through 10.5.1 contain a flaw in the bgpd daemon's handling of BGP NOTIFICATION Cease/Hard Reset messages (CWE-125). The bgp_notify_decapsulate_hard_reset() function does not check the length of the data field, so a one-byte field makes it read past a heap buffer, and its length value underflows. A remote BGP peer with an established session and negotiated Graceful Restart with the Notification bit can send such a message to crash bgpd, which terminates all BGP sessions.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| FRRouting | FRRouting | 10.5.0 to before 10.5.2; 10.4.0 to before 10.4.3; 10.3 to before 10.3.4; 10.2 to before 10.2.6; 10.1 to before 10.1.5; 8.3 to before 10.0.5 | 10.5.2, 10.4.3, 10.3.4, 10.2.6, 10.1.5, 10.0.5 | Patch available | CNA |
- FRRouting VendorFRRouting Affected 10.5.0 to before 10.5.2; 10.4.0 to before 10.4.3; 10.3 to before 10.3.4; 10.2 to before 10.2.6; 10.1 to before 10.1.5; 8.3 to before 10.0.5 Fixed in 10.5.2, 10.4.3, 10.3.4, 10.2.6, 10.1.5, 10.0.5 Patch available CNA
Remediation
Upgrade FRRouting to 10.0.5, 10.1.5, 10.2.6, 10.3.4, 10.4.3, 10.5.2 or 10.6.0, using the fixed release that matches the branch in use.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA FRRouting (FRRouting) Fixed in 10.5.2, 10.4.3, 10.3.4, 10.2.6, 10.1.5, 10.0.5
Timeline
- 2026-11-13 Threatist record created from CVE-2026-129217
- 2026-11-13 Alias added: GHSA-hgq9-rmfx-r8g6
- 2026-11-16 CISA SSVC decision points changed
References
More FRRouting vulnerabilities
- TI-2023-20107 FRRouting FRR 7.5.1 through 9.0 and Pica8 PICOS 4.3.3.2 allow a remote attacker to cause… CVSS 3.1HIGH 7.5
- TI-2023-21958 An issue was discovered in FRRouting FRR 9.0. CVSS 3.1CRITICAL 9.8
- TI-2024-29658 An issue was discovered in FRRouting (FRR) through 10.1. CVSS 3.1CRITICAL 9.8
- TI-2023-21957 An issue was discovered in FRRouting FRR through 9.0. CVSS 3.1CRITICAL 9.1
- TI-2023-19790 bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." CVSS 3.1CRITICAL 9.8
- TI-2022-17234 An out-of-bounds read in the BGP daemon of FRRouting FRR before 8.4 may lead to a… CVSS 3.1CRITICAL 9.1
Sources
- CVE-2026-129217 · CVE Program
- CVE-2026-129217 · NVD
- FIRST EPSS
- GHSA-hgq9-rmfx-r8g6 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences