CVE-2026-37457

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

An off-by-one out-of-bounds write vulnerability in the bgp_flowspec_op_decode() function (bgpd/bgp_flowspec_util.c) of FRRouting (FRR) stable/10.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted FlowSpec component.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

May 1, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 1, 2026
No patch confirmed yet.
generic

bgpd: fix off-by-one error in FlowSpec operator array bounds check · FRRouting/frr@0e6882b · GitHub

https://github.com/FRRouting/frr/commit/0e6882bc72c0278988a47b2f0f73b7a91099a25c

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntufrr-snmp (10.5.1-1ubuntu4.1) @ resolute2026-08-23ubuntu
redhatfrr10-0:10.4.3-3.el9_82026-06-08redhat
redhatfrr-0:8.5.3-13.el9_82026-06-08redhat
redhatfrr-0:10.4.4-1.el10_22026-06-08redhat
redhatfrr-0:7.5.1-24.el8_102026-06-08redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
frr10.0-0.1 ... 9.1-0.1 (59 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
frr8.4.2-1, 8.4.4-1, 8.4.4-1.1~deb12u18.4.4-1.1~deb12u2
Debian:13(1)
PackageVulnerable rangeFixed inDependents
frr10.3-310.3-3+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
frr10.3-3 ... 10.6.0-1 (19 versions)10.6.0-2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 6× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 236 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:53 UTCEPSS rescore
  4. 2026-09-01 04:39 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:41 UTCEPSS rescore
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 14:46 UTCEPSS rescore
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-23 21:43 UTCEG score recompute
  12. 2026-08-23 21:43 UTCVendor advisory
  13. 2026-08-23 21:43 UTCGHSA enrichment
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 13:19 UTCEG score recompute
  21. 2026-08-17 13:19 UTCVendor advisory
  22. 2026-08-17 13:19 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 05:14 UTCEG score recompute
  25. 2026-08-16 05:14 UTCVendor advisory
Show 75 more
  1. 2026-08-16 05:14 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 16:59 UTCVendor advisory
  5. 2026-08-14 16:59 UTCGHSA enrichment
  6. 2026-08-14 03:43 UTCEG score recompute
  7. 2026-08-14 03:43 UTCVendor advisory
  8. 2026-08-14 03:43 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 06:39 UTCVendor advisory
  11. 2026-08-13 06:39 UTCGHSA enrichment
  12. 2026-08-12 17:22 UTCEG score recompute
  13. 2026-08-12 17:22 UTCVendor advisory
  14. 2026-08-12 17:22 UTCGHSA enrichment
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 16:14 UTCEG score recompute
  17. 2026-08-11 16:14 UTCVendor advisory
  18. 2026-08-11 16:14 UTCGHSA enrichment
  19. 2026-08-11 01:46 UTCEG score recompute
  20. 2026-08-11 01:46 UTCVendor advisory
  21. 2026-08-11 01:46 UTCGHSA enrichment
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 05:08 UTCVendor advisory
  24. 2026-08-10 05:08 UTCGHSA enrichment
  25. 2026-08-09 15:59 UTCEG score recompute
  26. 2026-08-09 15:59 UTCVendor advisory
  27. 2026-08-09 15:59 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 02:50 UTCEG score recompute
  30. 2026-08-09 02:50 UTCVendor advisory
  31. 2026-08-09 02:50 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 04:45 UTCEG score recompute
  34. 2026-08-08 04:45 UTCVendor advisory
  35. 2026-08-08 04:45 UTCGHSA enrichment
  36. 2026-08-07 15:35 UTCVendor advisory
  37. 2026-08-07 15:35 UTCGHSA enrichment
  38. 2026-08-07 02:26 UTCEG score recompute
  39. 2026-08-07 02:26 UTCVendor advisory
  40. 2026-08-07 02:26 UTCGHSA enrichment
  41. 2026-08-06 13:46 UTCEPSS rescore
  42. 2026-08-06 11:48 UTCVendor advisory
  43. 2026-08-06 11:47 UTCGHSA enrichment
  44. 2026-08-05 22:34 UTCEG score recompute
  45. 2026-08-05 22:34 UTCVendor advisory
  46. 2026-08-05 22:34 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:38 UTCEPSS rescore
  50. 2026-08-03 20:16 UTCEG score recompute
  51. 2026-08-03 20:16 UTCVendor advisory
  52. 2026-08-03 20:16 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 18:45 UTCVendor advisory
  55. 2026-08-02 18:45 UTCGHSA enrichment
  56. 2026-08-02 05:36 UTCEG score recompute
  57. 2026-08-02 05:36 UTCVendor advisory
  58. 2026-08-02 05:36 UTCGHSA enrichment
  59. 2026-08-02 02:27 UTCEPSS rescore
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 01:30 UTCEPSS rescore
  63. 2026-07-27 14:13 UTCEPSS rescore
  64. 2026-07-26 14:54 UTCEPSS rescore
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-24 14:17 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-23 03:10 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:24 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-20 12:02 UTCOSV refresh
  75. 2026-07-19 14:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-37457?
CVE-2026-37457 is a high vulnerability published on May 1, 2026. An off-by-one out-of-bounds write vulnerability in the bgpflowspecopdecode() function (bgpd/bgpflowspec_util.c) of FRRouting (FRR) stable/10.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted FlowSpec component.
When was CVE-2026-37457 disclosed?
CVE-2026-37457 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-37457 actively exploited?
CVE-2026-37457 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.0% of all scored CVEs.
What is the CVSS score of CVE-2026-37457?
CVE-2026-37457 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-37457?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-37457, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-37457

Explore →

Is Your Infrastructure Affected by CVE-2026-37457?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.