PoC Monitor
← All CVEs
CVE-2026-129456published 14 Nov 2026 19:13 UTCData: JSON · API

Frrouting

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub · +1 suspicious, not counted
CVSS7.7high · scored by CNA · CWE-416
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

frrouting frrouting
  • >= 97dd9ea9e3e2aa982dcbc36466573eb4c0c87cbd, < *
  • >= 10.6.0, < 10.6.2

Fixed in *, 40f25e62686865649b7631ec30756f9661e12dd3, 10.6.2

Mitigation

Upgrade frrouting to * or 40f25e62686865649b7631ec30756f9661e12dd3 or 10.6.2 or later.

Workaround

Remove "neighbor <neighbor> soft-reconfiguration inbound", or configure "neighbor <neighbor> path-attribute discard 23" (or "neighbor <neighbor> path-attribute treat-as-withdraw 23") for neighbors that are not expected to send the Tunnel Encapsulation attribute, in particular all eBGP neighbors. With the attribute discarded, bgpd skips it without parsing or storing it.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published14 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

1 suspicious or fake

Suspicious or fake 1
RepositoryCreatedStarsAssessment
GHLists/new-cves 24 Sep 2026 −51 d 0 Suspicious · score 60
Why suspicious
  • owner account created less than 7 days before the repo
  • references an exfiltration/paste endpoint in data/new-cves-2026-09-25T14-18-58-335463Z.csv

Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.