Skip to content

NetworksHigh 8.2Patch available

CVE-2026-120221

Remote bgpd crash via double-free in FRRouting (dynamic neighbors + peer-group SoO).

How scary is it?

updated 14 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run frrouting in an affected version>= 01da2d26911c72023e71579bf4feeb707087ef50 and < * / >= 8.4.0 and < 10.2.7 / >= 10.3.0 and < 10.3.5 (+4 more)

    >= 01da2d26911c72023e71579bf4feeb707087ef50 and < * >= 8.4.0 and < 10.2.7 >= 10.3.0 and < 10.3.5 >= 10.4.0 and < 10.4.6 >= 10.5.0 and < 10.5.6 >= 10.6.0 and < 10.6.3 >= 10.7.0 and < 10.7.2

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack requirements: Present (AT:P). The attack depends on deployment or execution conditions. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenUpgrade FRR to the patched release or apply the fix; as interim remove Site-of-Origin from peer-groups or disable…

    Upgrade FRR to the patched release or apply the fix; as interim remove Site-of-Origin from peer-groups or disable listen-ranges.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. FRRouting bgpd crash can drop all BGP sessions; remotely triggerable with simple TCP connects. FRR is widely used in ISPs, cloud and enterprise networks — can cause major infrastructure outages.

CVSS
8.2Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.36%chance of exploitation in the next 30 daystop 70% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
13 Nov 2026analysed here 14 Nov 2026

Summary

Impact

Remote denial-of-service: attacker can crash bgpd and drop all BGP sessions by opening/closing TCP connections to port 179.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weaknesses
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
frrouting>= 01da2d26911c72023e71579bf4feeb707087ef50 and < *>= 8.4.0 and < 10.2.7>= 10.3.0 and < 10.3.5>= 10.4.0 and < 10.4.6>= 10.5.0 and < 10.5.6>= 10.6.0 and < 10.6.3>= 10.7.0 and < 10.7.2Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • FRRouting (bgpd) 8.4 and later
  • Routers and systems running FRR bgpd

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability is triggered remotely via the BGP protocol, which is not HTTP-based, so a web application firewall cannot filter the malicious input.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 13 Nov 2026Published
  2. 14 Nov 2026CVE record last updated1 day later
  3. 14 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-120221 being exploited?

Not confirmed. CVE-2026-120221 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-120221?

CVE-2026-120221 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-120221?

Yes. A fix has been recorded for CVE-2026-120221. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-120221 affect?

CVE-2026-120221 affects FRRouting (bgpd) 8.4 and later, Routers and systems running FRR bgpd. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-120221?

Upgrade FRR to the patched release or apply the fix; as interim remove Site-of-Origin from peer-groups or disable listen-ranges.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Patches (1)

  • github.com /FRRouting/frr/pull/21685/changes/6a96f515760dc278147fbf802777956ba80c7edd

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.