# CVE-2026-129456: Use after free in frrouting

> A BGP neighbor with soft-reconfiguration inbound can send crafted Tunnel Encapsulation attributes that make bgpd double-free, crashing it and dropping all sessions.

- **Severity:** High 7.7 (`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/AU:N/R:A`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** Yes
- **Published:** 14 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129456, GHSA-m8qq-j9p2-w4x8, UBUNTU-CVE-2026-129456

## What is CVE-2026-129456?

CVE-2026-129456 is a high-severity use after free vulnerability in frrouting, published on 14 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free), CWE-415 (Double Free)

## Which versions are affected by CVE-2026-129456?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-129456?

No fix published yet.

## Is CVE-2026-129456 being exploited?

There is no known exploitation of CVE-2026-129456 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129456 and fix it if it is affected.

What it is: CVE-2026-129456 is a high-severity use after free vulnerability in frrouting, published on 14 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129456 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: frrouting. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129456/ (Markdown: https://insights.sbomify.com/CVE-2026-129456/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129456
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129456
- OSV: https://osv.dev/vulnerability/CVE-2026-129456

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129456/
Summaries are generated and may contain mistakes; the official description above is the record.
