Skip to main content
CVE-2025-61103VulnerabilityPublished

CVE-2025-61103: frr · n/a

Affects frrSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 50% 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 28 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 2026-10-25.

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 project communications and security advisories for patches addressing CVE-2025-61103 and apply updates promptly once available. 2. Implement strict network segmentation and access controls to restrict OSPF traffic only to trusted devices and interfaces, minimizing exposure to potentially malicious packets. 3. Deploy filtering rules on routers and firewalls to block or rate-limit unexpected or malformed OSPF packets from untrusted sources. 4. Use network monitoring tools to detect unusual OSPF traffic patterns that could indicate exploitation attempts. 5. Consider deploying redundancy and failover mechanisms in routing infrastructure to maintain network availability if a device is impacted. 6. Conduct regular security assessments of network devices running FRR to ensure configurations follow best practices and minimize attack surface. 7. Educate network operations teams about this vulnerability and response procedures to quickly isolate affected devices if exploitation is suspected.

Description

FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_ext_link_lan_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…