# CVE-2025-61099: Null dereference in n/a

> Attackers can cause a Denial of Service in FRRouting by sending a crafted LS Update packet that triggers a NULL pointer dereference.

- **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:** 27 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** AZL-69619, AZL-69622, DEBIAN-CVE-2025-61099, GHSA-6xr9-vq37-4x64, UBUNTU-CVE-2025-61099

## What is CVE-2025-61099?

CVE-2025-61099 is a high-severity vulnerability in n/a, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FRRouting/frr from v2.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the opaque_info_detail function at ospf_opaque.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted LS Update packet.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-61099?

It affects 1 product.


Products: Frrouting Frrouting.

## How do I fix CVE-2025-61099?

Upgrade to a fixed version.

## Is CVE-2025-61099 being exploited?

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

## Other vulnerabilities in n/a

- [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-2025-61099 and fix it if it is affected.

What it is: CVE-2025-61099 is a high-severity vulnerability in n/a, published on 27 Oct 2025. 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-2025-61099 in the wild and no public exploit code.

Affected product: n/a. 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-2025-61099/ (Markdown: https://insights.sbomify.com/CVE-2025-61099/index.md)
```

## Sources

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

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