Read the docs

Use-after-free in FRRouting bgpd tunnel encapsulation attributes

Priority LOW 35CWE-415Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
Present
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-415 and the CVSS impact.

Summary

FRRouting versions from 10.6.0 before 10.6.2 are affected. The bgpd daemon frees the Tunnel Encapsulation attribute sub-TLVs while routes still point to them, a use after free (CWE-416). A BGP neighbor with an established session can trigger it when soft-reconfiguration inbound is configured for that neighbor, which makes bgpd abort and drop all BGP sessions, and memory corruption beyond a crash cannot be ruled out.

Written with Claude Haiku 5.5 from the sources below · 2026-11-15

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00283 21st percentileScored 2026-11-16
Fix Fixed frrouting (frrouting): 10.6.2

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
FRRoutingfrrouting10.6.0 to before 10.6.210.6.2Patch availableCNA
  • frrouting VendorFRRouting Affected 10.6.0 to before 10.6.2 Fixed in 10.6.2 Patch available CNA

Remediation

Upgrade FRRouting to version 10.6.2.

Written with Claude Haiku 5.5 from the sources below · 2026-11-15

  • Fix · CNA frrouting (frrouting) Fixed in 10.6.2

Timeline

  1. 2026-11-14 Threatist record created from CVE-2026-129456
  2. 2026-11-14 Alias added: GHSA-m8qq-j9p2-w4x8
  3. 2026-11-15 Title updated · CNA
  4. 2026-11-15 CVSS score changed · CNA
  5. 2026-11-15 Fix available: frrouting/[email protected] · CNA
  6. 2026-11-15 2 new references · CNA
  7. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2023-20107 FRRouting FRR 7.5.1 through 9.0 and Pica8 PICOS 4.3.3.2 allow a remote attacker to cause… CVSS 3.1HIGH 7.5
  • TI-2023-21958 An issue was discovered in FRRouting FRR 9.0. CVSS 3.1CRITICAL 9.8
  • TI-2024-29658 An issue was discovered in FRRouting (FRR) through 10.1. CVSS 3.1CRITICAL 9.8
  • TI-2023-21957 An issue was discovered in FRRouting FRR through 9.0. CVSS 3.1CRITICAL 9.1
  • TI-2023-19790 bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." CVSS 3.1CRITICAL 9.8
  • TI-2022-17234 An out-of-bounds read in the BGP daemon of FRRouting FRR before 8.4 may lead to a… CVSS 3.1CRITICAL 9.1
See all 53 →

Sources