Skip to main content
VulnerabilityPublished Updated

CVE-2025-61102: frr · NULL Pointer Dereference

Affects frrSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfrrouting/frrpkg:github/frrouting/frrOther threatsAffected
  • =4.0
  • <=10.4.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Monitor FRRouting vendor channels closely for official patches addressing CVE-2025-61102 and apply them immediately upon release.
  2. Implement network-level filtering to block or rate-limit OSPF packets from untrusted or external sources, reducing exposure to crafted malicious packets.
  3. Employ segmentation and strict access controls on routing protocol traffic to limit which devices can send OSPF packets to FRRouting instances.
  4. Enable and enhance logging and monitoring of FRRouting daemons to detect abnormal crashes or restarts indicative of exploitation attempts.
  5. Consider deploying redundant routing paths and failover mechanisms to maintain network availability in case of a DoS event.
  6. Conduct internal vulnerability assessments and penetration tests simulating crafted OSPF packets to evaluate exposure and response readiness.
  7. Educate network operations teams about this vulnerability and establish incident response procedures specific to routing daemon failures. These steps go beyond generic advice by focusing on network protocol filtering, operational monitoring, and resilience planning tailored to FRRouting and OSPF environments.

Description

FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_ext_link_adj_sid function at ospf_ext.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted OSPF packet.

References

Community reviews

Loading reviews…