UBUNTU-CVE-2026-129456: High severity ubuntu/quagga vulnerability

Published Nov 16, 2026
·
Updated

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.

Affected Software

8 affected components
ubuntu/quagga*
ubuntu/quagga*
ubuntu/quagga*
ubuntu/frr*
ubuntu/frr*
ubuntu/frr*
ubuntu/frr*
ubuntu/frr*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Discard Tunnel Encapsulation attribute type 23 from eBGP sessions.

Event History

Nov 16, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are exposed to exploitation?

Exposure requires bgpd to receive affected route updates from a BGP neighbor while "soft-reconfiguration inbound" is configured for that neighbor. The issue is triggered through Tunnel Encapsulation attributes (type 23).

2

What access does an attacker need?

An attacker needs the ability to send crafted BGP updates from a configured neighbor. No user interaction is required, but the attacker must have the low-privilege access represented by a BGP neighbor relationship.

3

What can be done if patching cannot happen immediately?

Remove or avoid "soft-reconfiguration inbound" on neighbors that could send the affected updates, where operationally feasible. This configuration is part of the condition required to trigger the flaw.

4

How might an active attack appear operationally?

In the reported non-AddressSanitizer build, bgpd hit an assertion failure in memory accounting, aborted, and dropped all BGP sessions on the router. A malicious neighbor can repeat the condition after bgpd restarts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203