CVE-2026-120033: frr: bgpd Send Hold Timer expiry bypasses the FSM, leaving a phantom Established session or crashing bgpd with Graceful Restart
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: frrouting frrouting 10.4.6, 10.5.6, 10.6.3; azl4 frr 10.4.4-5.azl4 on Azure Linux 4.0 Release Notes.
Low priority for now. Upgrade to frrouting frrouting 10.4.6, 10.5.6, 10.6.3; azl4 frr 10.4.4-5.azl4 on Azure Linux 4.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 12, 2026
- Updated
- Nov 14, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-372
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · NetDEF
- 6.0
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:L/AU:N/R:A
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (NetDEF). Independent of NVD's CPE analysis and usually ahead of it.
frrouting frrouting
- 4967bf6d729d7dd14dff7b672b2fd4afe78a0d86 and lateraffected · gitfixed in 57a7f3eb48837359d6e3ee5ebd4acea8f49320e5
- 10.1.0 and later · before 10.4.6affected · semver
- 10.5.0 and later · before 10.5.6affected · semver
- 10.6.0 and later · before 10.6.3affected · semver
- 10.7.0 and later · before 10.7.2affected · semver
Same product
frrouting: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-38406bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow."39Monitor
- CVE-2023-41361An issue was discovered in FRRouting FRR 9.0.39Monitor
- CVE-2022-37032An out-of-bounds read in the BGP daemon of FRRouting FRR before 8.4 may lead to a segmentation fault and denial of service.37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2022-42917Sep 14, 2026 · In FRRouting FRR before 8.5, the service user (usually frr) can escalate its privileges to root by monitoring the configuration directory…26Monitor
- ← EarlierCVE-2026-119776Nov 4, 2026 · frr: ospf6d fails to enforce all OSPFv3 packets use IPv6 link-local addresses24Monitor
- Later →CVE-2026-120221Nov 13, 2026 · frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| frrouting frrouting | 10.4.6 | Vendor (CNA) |
| frrouting frrouting | 10.5.6 | Vendor (CNA) |
| frrouting frrouting | 10.6.3 | Vendor (CNA) |
| frrouting frrouting | 10.7.2 | Vendor (CNA) |
| frrouting frrouting | 57a7f3eb48837359d6e3ee5ebd4acea8f49320e5 | Vendor (CNA) |
| azl4 frr 10.4.4-5.azl4 on Azure Linux 4.0 | Release Notes | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026+3 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-372 · Incomplete Internal State DistinctionCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:A/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.