# CVE-2022-26128: Memory corruption in FRRouting

> A buffer overflow in FRRouting's Babel protocol allows remote attackers to execute arbitrary code or cause a denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2022
- **Updated:** 4 Nov 2025
- **Also known as:** CLEANSTART-2025-RF72378, DEBIAN-CVE-2022-26128, GHSA-6w5w-27h7-6r2x, UBUNTU-CVE-2022-26128

## What is CVE-2022-26128?

CVE-2022-26128 is a high-severity memory corruption vulnerability in FRRouting, published on 3 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A buffer overflow vulnerability exists in FRRouting through 8.1.0 due to a wrong check on the input packet length in the babel_packet_examin function in babeld/message.c.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2022-26128?

It affects 1 product.


Products: Frrouting Frrouting.

## How do I fix CVE-2022-26128?

Upgrade to a fixed version.

## Is CVE-2022-26128 being exploited?

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

## Other vulnerabilities in FRRouting

- [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-26129](https://insights.sbomify.com/CVE-2022-26129/): Memory corruption in FRRouting (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26128 and fix it if it is affected.

What it is: CVE-2022-26128 is a high-severity memory corruption vulnerability in FRRouting, published on 3 Mar 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-26128 in the wild and no public exploit code.

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-2022-26128/ (Markdown: https://insights.sbomify.com/CVE-2022-26128/index.md)
```

## Sources

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

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