Quick answers
- Is CVE-2026-37460 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-37460 being exploited in the wild.
- How severe is CVE-2026-37460?
- Informational severity, with a CVSS score of 0, published 3 June 2026.
- Which products and versions are affected?
- Frrouting stable/10.0 to stable/10.6.
- Is there a fix for CVE-2026-37460?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-37460 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-37460?
- Check whether you run Frrouting at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the rfapiRibBi2Ri() function within rfapi_rib.c of FRRouting (FRR) versions stable/10.0 through stable/10.6. The flaw is caused by insufficient input validation when handling BGP UPDATE messages, specifically related to EVPN and ENCAP/VNC packet parsing. A remote attacker can exploit this by sending a crafted BGP UPDATE message to a vulnerable instance, leading to a service crash (Denial of Service). A fix has been identified in the project's source code repository to improve packet validation.
Affected products
- FRRouting FRRouting stable/10.0 to stable/10.6
Timeline
- 2026-06-03: disclosed
- 2026-06-03: advisory