CVE-2026-120221
Last modified
CVE-2026-120221 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
Description
In FRRouting, bgpd frees the same memory twice when dynamic BGP neighbors disconnect, if the peer-group used by a "bgp listen range" also has a Site-of-Origin configured ("neighbor PG soo"). Each dynamic neighbor shares the peer-group's SoO value instead of getting its own copy, but frees it as its own when the neighbor is deleted, which happens as soon as its connection closes. The first disconnect leaves the peer-group pointing at freed memory, and the second disconnect frees it again, causing bgpd to abort and drop all BGP sessions on the router. Any host whose address falls inside the listen range can trigger this by opening and closing two TCP connections to the BGP port, without sending any BGP message and without knowing the AS number, and can repeat it each time bgpd restarts. If the peer-group has a TCP-MD5 password, only hosts that know the password can trigger it. Two ordinary flaps of legitimate dynamic neighbors have the same effect. Between the two frees, displaying the configuration ("show running-config") or establishing a dynamic neighbor also reads the freed memory, which can crash bgpd after a single disconnect. Only configurations that combine a listen range with a SoO on the same peer-group are affected.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| frrouting | frrouting | >= 01da2d26911c72023e71579bf4feeb707087ef50, < *; >= 8.4.0, < 10.2.7; >= 10.3.0, < 10.3.5; >= 10.4.0, < 10.4.6; >= 10.5.0, < 10.5.6; >= 10.6.0, < 10.6.3; >= 10.7.0, < 10.7.2 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-120221?
How severe is CVE-2026-120221?
How do I fix CVE-2026-120221?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-120214@fastify/http-proxy is a Fastify plugin that proxies HTTP re…5.9
- CVE-2026-120215@fastify/cors is the CORS plugin for the Fastify web framewo…3.7
- CVE-2026-120216fastify is a web framework for Node.js. In versions 5.8.0 th…5.9
- CVE-2026-120217A vulnerability was detected in Delgan loguru 0.7.3. The aff…4.3
- CVE-2026-120218A flaw has been found in Typemill up to 2.26.0. The impacted…3.5
- CVE-2026-12022Race in Safe Browsing in Google Chrome on Mac prior to 149.0…8.3
- CVE-2026-120222undici is an HTTP client for Node.js. In versions 7.0.0 thro…5.9
- CVE-2026-120223A vulnerability was identified in Oray Pugongying X5 Pro up …3.1
- CVE-2026-120224A security flaw has been discovered in Oray Pugongying X5 Pr…9.9
- CVE-2026-120225A weakness has been identified in Oray Pugongying X5 Pro up …9.1
- CVE-2026-120226A security vulnerability has been detected in Hangzhou Xiong…3.3
- CVE-2026-120227A vulnerability was detected in WAVLINK WN701AE M01AE_V26010…9.9
Are you affected by CVE-2026-120221?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
