FRRouting bgpd leaves BGP sessions up after Send Hold Timer expiry
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · Low · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-617.
Summary
FRRouting bgpd from 10.1.0 before 10.4.6, from 10.5.0 before 10.5.6, from 10.6.0 before 10.6.3, and from 10.7.0 before 10.7.2 does not correctly close a BGP session when the Send Hold Timer expires, yet bgpd still treats the session as up (CWE-372). Any established neighbor that keeps sending KEEPALIVEs but stops reading while the router has much data to send can trigger this. If the neighbor announced Graceful Restart, bgpd crashes and takes down all BGP sessions on the router, and the neighbor can repeat this after each restart. Otherwise the session stays Established with the neighbor's routes installed until an operator clears it manually.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
Description from the CNA
In FRRouting, bgpd does not correctly close a BGP session when the Send Hold Timer (RFC 9687) expires, i.e. when a neighbor has stopped accepting data from the router for twice the hold time. The connection is closed, but bgpd still considers the session to be up. A BGP neighbor that keeps sending KEEPALIVEs but stops reading from its connection, at a time when the router has a large amount of data to send to it (for example while sending it a full routing table), can trigger this. If the neighbor announced Graceful Restart support, bgpd crashes shortly after the session is closed, taking down all BGP sessions on the router, and the neighbor can repeat this each time bgpd restarts. Otherwise, the session stays stuck in the Established state: the neighbor's routes stay installed and keep being advertised to other peers, and the neighbor cannot reconnect until an operator clears the session manually. The neighbor does not need to be malicious; an overloaded or stuck peer can trigger the same behavior. No special configuration is required: any established BGP neighbor can trigger the issue, and Graceful Restart helper mode, which leads to the crash, is enabled by default.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| FRRouting | frrouting | 10.1.0 to before 10.4.6; 10.5.0 to before 10.5.6; 10.6.0 to before 10.6.3; 10.7.0 to before 10.7.2 | 10.4.6, 10.5.6, 10.6.3, 10.7.2 | Patch available | CNA |
- frrouting VendorFRRouting Affected 10.1.0 to before 10.4.6; 10.5.0 to before 10.5.6; 10.6.0 to before 10.6.3; 10.7.0 to before 10.7.2 Fixed in 10.4.6, 10.5.6, 10.6.3, 10.7.2 Patch available CNA
Remediation
Upgrade FRRouting to 10.4.6, 10.5.6, 10.6.3 or 10.7.2, matching the release branch in use.
Written with Claude Haiku 5.5 from the sources below · 2026-11-14
- Fix · CNA frrouting (frrouting) Fixed in 10.4.6, 10.5.6, 10.6.3, 10.7.2
Timeline
- 2026-11-12 Threatist record created from CVE-2026-120033
- 2026-11-12 Alias added: GHSA-hgqg-fv3w-2x5g
- 2026-11-14 Fix available: frrouting/[email protected], frrouting/[email protected], frrouting/[email protected] +1 · CNA
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-120033 · CVE Program
- CVE-2026-120033 · NVD
- FIRST EPSS
- GHSA-hgqg-fv3w-2x5g · 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