Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.4

CVE-2026-129456: FRR BGP daemon can crash when processing tunnel attributes

CVE-2026-129456 · published 7 days ago
Summary

FRRouting's BGP service may stop unexpectedly if it receives a certain tunnel encapsulation attribute from a neighbor that has soft‑reconfiguration inbound enabled. The crash drops all BGP sessions on the router, potentially affecting network routing. Apply the latest FRR update or disable soft‑reconfiguration inbound to prevent the problem.

What to do
  • Update frrouting frrouting to version 1238ac4a06e5c23595e8bf626856f297d0c302a2.
  • Update debian frr to version 10.7.0-1.
Affected software
Ecosystem VendorProductAffected versions
– frrouting frrouting < *
Fix: upgrade to 1238ac4a06e5c23595e8bf626856f297d0c302a2
Debian:12 debian frr All versions
Debian:14 debian frr < 10.7.0-1
Fix: upgrade to 10.7.0-1
Ubuntu:Pro:16.04:LTS canonical quagga All versions
Ubuntu:Pro:20.04:LTS canonical frr All versions
Original advisory text
frr: bgpd use-after-free of Tunnel Encapsulation sub-TLVs via the attribute intern reuse cache with soft-reconfiguration inbound
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.
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
9.4 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-416Use After Free
CWE-415Double Free
Timeline
Published14 Nov 2026
Updated22 Nov 2026
First seen14 Nov 2026
Track software like this
Free during beta