CVE-2025-61106: frr · NULL Pointer Dereference
Affects frrSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 26 Oct 2026, 09:15 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubfrrouting/frrpkg:github/frrouting/frrOther threats | Affected
| 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 vendor announcements and apply official patches or updates for FRRouting as soon as they become available to address CVE-2025-61106. 2. Restrict OSPF packet sources by implementing access control lists (ACLs) or firewall rules to limit OSPF traffic to trusted devices and network segments only. 3. Segment network infrastructure to isolate routing protocol traffic from untrusted or less secure network zones, reducing exposure to crafted packets. 4. Employ network monitoring and anomaly detection tools to identify unusual OSPF packet patterns or spikes that could indicate exploitation attempts. 5. Conduct regular audits of network device configurations to ensure that only necessary routing protocols are enabled and properly secured. 6. Consider deploying redundancy and failover mechanisms in routing infrastructure to minimize service disruption in case of device failure. 7. Educate network operations teams about this vulnerability and encourage vigilance for signs of routing instability or device crashes. 8. If possible, temporarily disable OSPF on devices that are not critical or replace FRRouting with alternative routing software until patches are available.
Description
FRRouting/frr from v4.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the show_vty_ext_pref_pref_sid function at ospf_ext.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted OSPF packet.