# CVE-2026-28532: FRRouting < 10.5.3 Integer Overflow in OSPF TLV Parser Functions

> Attackers with OSPF adjacency can crash routers via crafted LS Update packets due to an integer overflow in TLV parsing.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Apr 2026
- **Updated:** 1 Oct 2026
- **Also known as:** AZL-85332, DEBIAN-CVE-2026-28532, GHSA-wjc3-2qjv-c8fp, UBUNTU-CVE-2026-28532

## What is CVE-2026-28532?

CVE-2026-28532 is a medium-severity vulnerability in FRRouting frr, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FRRouting before 10.5.3 contains an integer overflow vulnerability in seven OSPF Traffic Engineering and Segment Routing TLV parser functions where a uint16_t accumulator variable truncates uint32_t values returned by the TLV_SIZE() macro, causing the loop termination condition to fail while pointer advancement continues unchecked. Attackers with an established OSPF adjacency can send a crafted LS Update packet with a malicious Type 10 or Type 11 Opaque LSA to trigger out-of-bounds memory reads and crash all affected routers in the OSPF area or autonomous system.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Frrouting Frrouting.

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

Upgrade to a fixed version.

## Is CVE-2026-28532 being exploited?

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

## Other vulnerabilities in FRRouting frr

- [CVE-2024-44070](https://insights.sbomify.com/CVE-2024-44070/): Denial of service in n/a (critical 9.8)
- [CVE-2023-38406](https://insights.sbomify.com/CVE-2023-38406/): bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a "flowspec overflow." (critical 9.8)
- [CVE-2022-37035](https://insights.sbomify.com/CVE-2022-37035/): Use after free in n/a (high 8.1)
- [CVE-2022-26127](https://insights.sbomify.com/CVE-2022-26127/): Memory corruption in FRRouting (high 7.8)
- [CVE-2022-26128](https://insights.sbomify.com/CVE-2022-26128/): Memory corruption in FRRouting (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28532 is a medium-severity vulnerability in FRRouting frr, published on 30 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28532 in the wild and no public exploit code.

Affected product: FRRouting frr. 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-28532/ (Markdown: https://insights.sbomify.com/CVE-2026-28532/index.md)
```

## Sources

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

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