CVE-2025-61099

Exp

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.

Published: 2025-10-27 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-61099 is rated Exploit Available (58.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.18%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-61099

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-61099

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-13 0.14% 0.18% +0.04%
2 2026-05-11 0.18% 0.14% -0.04%
3 2026-04-06 — 0.18% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-61099

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-61099

OS Trackers for CVE-2025-61099

vendor priority summary link
debian not yet assigned CVE-2025-61099 not yet assigned priority: Debian including 1 source packages (frr), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-61099
redhat medium — https://access.redhat.com/security/cve/CVE-2025-61099
suse medium CVE-2025-61099 severity moderate: SUSE including 54 source package names (frr-10.2.1-150700.3.5.1, frr-10.2.1-4.1, …), 211 product×package rows across 32 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (32 product lines)): Known Not Affected 163, Fixed 37, First Fixed 11. https://www.suse.com/security/cve/CVE-2025-61099/
ubuntu medium CVE-2025-61099 medium priority: Ubuntu including 2 source packages (frr, quagga), 14 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): DNE 4, released 4, needed 3, ignored 2, needs-triage 1. https://ubuntu.com/security/CVE-2025-61099

Affected software / configurations for CVE-2025-61099

Vendor Product Version Raw CPE
frrouting frrouting >= 2.0, <= 10.4.1 cpe:2.3:a:frrouting:frrouting:*:*:*:*:*:*:*:*

References for CVE-2025-61099

cvelogic Threat Intelligence