CVE-2026-65624

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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, secondary
Trending — 4 sources updated this week
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1.

The HTTP/1.1 handler in cowboy_http enforces the max_headers limit by counting the number of distinct header names in a map (maps:size(Headers)). When a request contains multiple header lines with the same name, the values are concatenated into a single ever-growing binary stored under that one map key (", " for regular headers, "; " for cookies), so the map size stays at one and the max_headers cap (default 100) is never reached. Because no accumulator bounds the total number of header lines or the total byte size of the header block (only per-line max_header_name_length and max_header_value_length apply), an unauthenticated client can send an arbitrary number of header lines with the same name and grow the connection process's binary memory to arbitrary size within the request window.

The impact per connection is bounded by request_timeout (default 5 seconds, not reset by header data), and by max_heap_size when set (the offending connection process is killed once its heap grows past the limit). When max_heap_size is left at the default (unset), sustained abuse can drive the Erlang VM into out-of-memory conditions.

This issue affects cowboy from 2.0.0-pre.4 before 2.18.0.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 28, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-65624
github_commit

commit 3a34d8c1cfd9 (ninenines/cowboy)

Fix landed in ninenines/cowboy commit 3a34d8c1cfd9 — awaiting tagged release

https://github.com/ninenines/cowboy/commit/3a34d8c1cfd94326466aa16a9017236691dc9c55
generic

Cowboy HTTP/1.1 max_headers Bypass via Duplicate Header Names Enables Memory Exhaustion | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-65624.html

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrabbitmq-server4-3-main-4.3.5-0.1.hum12026-08-21redhat
redhatrabbitmq-server4-3-main-4.3.4-0.2.hum12026-07-28redhat
redhatrabbitmq-server4-2-main-4.2.9-0.2.hum12026-07-28redhat

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

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
erlang-cowboy0.10.0+dfsg1-1 ... 2.17.0+dfsg-1 (15 versions)2.18.0+dfsg-1
Hex(1)
PackageVulnerable rangeFixed inDependents
cowboy2.0.0 ... 2.9.0 (26 versions)2.18.0

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 21× in last 7d / 96× 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 193 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-65624?
CVE-2026-65624 is a medium vulnerability published on July 28, 2026. Allocation of Resources Without Limits or Throttling vulnerability in ninenines cowboy allows an unauthenticated remote attacker to exhaust connection process memory over HTTP/1.1. The HTTP/1.1 handler in cowboyhttp enforces the maxheaders limit by counting the number of distinct header names in a…
When was CVE-2026-65624 disclosed?
CVE-2026-65624 was first published in the National Vulnerability Database on July 28, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65624 actively exploited?
CVE-2026-65624 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 67.8% of all scored CVEs.
What is the CVSS score of CVE-2026-65624?
CVE-2026-65624 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-65624?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65624, 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-65624

Explore →

Is Your Infrastructure Affected by CVE-2026-65624?

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