# CVE-2022-26125: Memory corruption in FRRouting

> A buffer overflow in FRRouting's IS-IS protocol allows attackers to execute arbitrary code or cause denial of service via crafted packets.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Mar 2022
- **Updated:** 4 Nov 2025
- **Also known as:** ALSA-2022:8112, CLEANSTART-2025-DQ89362, DEBIAN-CVE-2022-26125, GHSA-9hg8-8wq3-mhhg, RHSA-2022:8112, RLSA-2022:8112, UBUNTU-CVE-2022-26125

## What is CVE-2022-26125?

CVE-2022-26125 is a high-severity memory corruption vulnerability in FRRouting, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow vulnerabilities exist in FRRouting through 8.1.0 due to wrong checks on the input packet length in isisd/isis_tlvs.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-26125?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `frr` | AlmaLinux:9 | All versions | 8.2.2-4.el9 |
| `frr` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.2.2-4.el9 |
| `frr-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.2.2-4.el9 |
| `frr-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:8.2.2-4.el9 |
| `frr` | Rocky Linux:9 | All versions | 0:8.2.2-4.el9 |

Products: Frrouting Frrouting.

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

Apply the vendor's patch.

## Is CVE-2022-26125 being exploited?

There is no known exploitation of CVE-2022-26125 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-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-2022-26125 and fix it if it is affected.

What it is: CVE-2022-26125 is a high-severity memory corruption vulnerability in FRRouting, published on 3 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-26125 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-26125/ (Markdown: https://insights.sbomify.com/CVE-2022-26125/index.md)
```

## Sources

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

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