Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-120221frr: bgpd double free of peer-group Site-of-Origin when dynamic neighbors disconnect

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.

Timeline

  1. ID reserved

    By NetDEF

  2. · 13 days later

    Published

  3. · 4 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-120221, by who scored it
Scored byCVSSScoreVector
NetDEFCNA (assigner)4.0High8.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:N/R:A
NVDNVD · Awaiting Analysis4.0High8.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/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
EPSS (exploitation in 30 days)
0.28% · top 80% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.2.

Affected products

  • frrouting · frrouting

    • affected 01da2d26911c72023e71579bf4feeb707087ef50 – < *
    • affected 8.4.0 – < 10.2.7
    • affected 10.3.0 – < 10.3.5
    • affected 10.4.0 – < 10.4.6
    • affected 10.5.0 – < 10.5.6
    • affected 10.6.0 – < 10.6.3
    • affected 10.7.0 – < 10.7.2

What to do

Workaround: Do not configure "neighbor <peer-group> soo" on a peer-group used by "bgp listen range". Instead, set the SoO extended community with an inbound route-map, or set "neighbor soo" on statically configured neighbors. Configuring a TCP-MD5 "password" on the peer-group limits the trigger to hosts that know the key.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-120221 badge
[![CVE-2026-120221](https://cveledger.app/badge/CVE-2026-120221.svg)](https://cveledger.app/cve/CVE-2026-120221)

Record last updated .