CVE-2026-129456

7.7High

Published 14 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.7CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
Low
User action
None
Impact
Full C/I/A compromise
Weakness
CWE-415, CWE-416

What an attacker gets

Authenticated BGP neighbors can crash the bgpd process, causing a total BGP session drop and potential remote code execution. An attacker needs an established BGP session with 'soft-reconfiguration inbound' enabled.

Root cause

A double-free vulnerability occurs because the bgpd process incorrectly manages the reference counting of Tunnel Encapsulation attribute sub-TLVs during route processing.

Affected versions

FRRouting versions where 'soft-reconfiguration inbound' is enabled.

CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/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

Fix & remediation

Upgrade to a version containing the fix from PR 22008. Immediately disable 'soft-reconfiguration inbound' for all BGP neighbors in your frr.conf.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

In FRRouting, bgpd frees the sub-TLV chain of a Tunnel Encapsulation attribute (type 23) while routes stored by bgpd still point to it, if the attribute is received from a neighbor that has "soft-reconfiguration inbound" configured. A cache added to speed up attribute interning while processing the prefixes of an UPDATE checks whether an interned attribute set may be reused by comparing the parsed attributes with themselves, so the check always succeeds. Interning the parsed attributes for the Adj-RIB-In removes the Tunnel Encapsulation sub-TLVs from them, and the copy that bgpd then interns for the route reuses the cached attribute set, which still holds the sub-TLVs, without taking a reference on them. When the route is later replaced, withdrawn or cleared, for example when the session goes down, the sub-TLV chain is freed while still in use, and bgpd then reads it, decrements a reference count inside it and frees it a second time. In the reporter's build without AddressSanitizer this ended in an assertion failure in bgpd's memory accounting, aborting bgpd and dropping all BGP sessions on the router, and the neighbor can repeat it each time bgpd restarts. Because freed heap memory is written to and freed again, consequences beyond a crash cannot be ruled out. An established BGP session is required, and the attribute does not need to be malformed. bgpd processes attribute 23 from every neighbor, including eBGP neighbors, unless it is explicitly discarded, although RFC 9012 requires it to be filtered on eBGP sessions by default. Neighbors without "soft-reconfiguration inbound" are not affected.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-129456