CVE-2026-37461

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
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 out-of-bounds read in the ParseIP6Extended function (/bgp/bgp.go) of gobgp v4.3.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted BGP UPDATE message.

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
27%
KEV
Not listed

Published

May 4, 2026

Last Modified

May 11, 2026

Advisory Details (3)

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

packet/bgp: fix uint16 underflow in BGPUpdate.DecodeFromBytes · osrg/gobgp@9ce8936 · GitHub

https://github.com/osrg/gobgp/commit/9ce8936672ebc07df524da77fa4c6ae26d92be6d
generic

packet/bgp: fix insufficient length check in ParseIP6Extended · osrg/gobgp@362cce3 · GitHub

https://github.com/osrg/gobgp/commit/362cce3e325f56e7a4f792ccb9689b3bdda9e682
generic

gobgp/pkg/packet/bgp/bgp.go at v4.3.0 · osrg/gobgp · GitHub

https://github.com/osrg/gobgp/blob/v4.3.0/pkg/packet/bgp/bgp.go

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntugolang-github-osrg-gobgp-dev (3.36.0-2ubuntu0.1~esm1) @ resolute2026-08-23ubuntu

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
gobgp2.25.0-2 ... 4.7.0-1~bpo13+1 (31 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
gobgp3.10.0-1 ... 4.8.0-2~exp1 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gobgp3.36.0-2 ... 4.8.0-2~exp1 (12 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gobgp3.36.0-2, 4.3.0-14.4.0-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/osrg/gobgp/v4—4.4.0—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 198 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-37461?
CVE-2026-37461 is a high vulnerability published on May 4, 2026. An out-of-bounds read in the ParseIP6Extended function (/bgp/bgp.go) of gobgp v4.3.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted BGP UPDATE message.
When was CVE-2026-37461 disclosed?
CVE-2026-37461 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on May 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-37461 actively exploited?
CVE-2026-37461 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-37461?
CVE-2026-37461 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-37461?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-37461, 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-37461

Explore →

Is Your Infrastructure Affected by CVE-2026-37461?

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

Start Free Scan →Browse All CVEs