CVE-2026-56810

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-41862 (ENISA EUVD)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint (Mint.HTTP1 module) allows a denial of service via an oversized chunked transfer-encoded response.

This vulnerability is associated with program files lib/mint/http1.ex and program routines 'Elixir.Mint.HTTP1':decode_body/5, 'Elixir.Mint.HTTP1':add_body_to_buffer/2.

When Mint decodes a chunked HTTP response body, it accumulates each partial fragment of the current chunk in the connection's data_buffer (an unbounded iolist) via add_body_to_buffer/2 and does not emit the data to the caller until the full declared chunk length has been received. The chunk size is taken directly from the server and parsed with no upper bound, so a malicious or compromised server can announce one enormous chunk (for example a size line of 7FFFFFFF, about 2 GiB) and then send the body bytes slowly without ever completing the chunk. The client buffers every received byte while it waits for a completion that never arrives, and because no data responses are produced until the chunk finishes, a caller that otherwise streams large content-length bodies safely gains no protection. An unauthenticated remote server (reachable whenever a client follows redirects, fetches user-supplied URLs, or processes webhooks) can drive the client's memory arbitrarily high and trigger an out-of-memory condition.

This issue affects mint: from 0.5.0 before 1.9.1.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 6, 2026

Last Modified

October 25, 2026

Advisory Details (4)

Auto-updated Jul 6, 2026
Patch available. Sources: github_commit, github.
Web page

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-56810
GitHub advisoryMentions a patch (unverified)

Chunked response decoder buffers an entire chunk in memory before emitting it · Advisory · elixir-mint/mint · GitHub

https://github.com/elixir-mint/mint/security/advisories/GHSA-c59h-fq4p-r36r
GitHub commit

commit 193ce714907d (elixir-mint/mint)

Fix landed in elixir-mint/mint commit 193ce714907d — awaiting tagged release

https://github.com/elixir-mint/mint/commit/193ce714907d16e8adc4ab3c40e4f0c2f045b2a6
Web page

mint buffers an entire chunked response chunk in memory in Mint.HTTP1.decode_body/5 | Erlang Ecosystem Foundation CNA

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

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
mint0.5.0 ... 1.9.0 (19 versions)
  • 0.5.0 up to 1.9.1: fixed in 1.9.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 169 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 69 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-56810?
CVE-2026-56810 is a high-severity vulnerability; its CVE record was published on July 6, 2026. Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint (Mint.HTTP1 module) allows a denial of service via an oversized chunked transfer-encoded response. This vulnerability is associated with program files lib/mint/http1.ex and program routines…
When was the CVE record for CVE-2026-56810 published?
The CVE record for CVE-2026-56810 was published on July 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56810 actively exploited?
CVE-2026-56810 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56810?
CVE-2026-56810 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56810?
A fix for CVE-2026-56810 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56810?

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