BGP daemon crash via martian next hop
Published May 4, 2026 · Updated May 4, 2026
Improper input validation in FRRouting 10.0 through 10.6.0 allows remote authenticated users to crash bgpd via a crafted BGP UPDATE. The bgp_mp_reach_parse function accepts an IPv4 martian next hop in an MP_REACH_NLRI attribute instead of treating the route as withdrawn. The attacker must be an authenticated BGP peer able to supply the attribute; the consequence is routing-service interruption.
Summary
What happened
Improper input validation in FRRouting 10.0 through 10.6.0 allows remote authenticated users to crash bgpd via a crafted BGP UPDATE. The bgp_mp_reach_parse function accepts an IPv4 martian next hop in an MP_REACH_NLRI attribute instead of treating the route as withdrawn. The attacker must be an authenticated BGP peer able to supply the attribute; the consequence is routing-service interruption.
The record
- CVE
- CVE-2026-37458
- Published
- May 4, 2026
- Updated
- May 4, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 4, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo