Route manipulation via inconsistent EVPN NLRI lengths
Published Mar 30, 2026 · Updated Mar 30, 2026
Improper input validation in FRRouting FRR 10.5.0 through 10.5.1 allows remote authenticated users to manipulate EVPN routes. process_type2_route in bgpd/bgp_evpn.c validates psize and ipaddr_len separately but fails to require a consistent Type-2 NLRI layout before label parsing. Exploitation requires a legitimate BGP peer with L2VPN EVPN enabled and can corrupt routing state or cause a limited service interruption.
Summary
What happened
Improper input validation in FRRouting FRR 10.5.0 through 10.5.1 allows remote authenticated users to manipulate EVPN routes. process_type2_route in bgpd/bgp_evpn.c validates psize and ipaddr_len separately but fails to require a consistent Type-2 NLRI layout before label parsing. Exploitation requires a legitimate BGP peer with L2VPN EVPN enabled and can corrupt routing state or cause a limited service interruption.
The record
- CVE
- CVE-2026-5107
- Published
- Mar 30, 2026
- Updated
- Mar 30, 2026
- Vendor
- FRRouting
- Product
- FRRouting
- Classifications
- CWE-284, CWE-266
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 30, 2026CVE publishedPublication date reported by the CVE source.
- Mar 30, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.5.0
- Affected versionversion=10.5.1
What conditions does exploitation require?
What is affected?
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.
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