CVE-2026-91043

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). 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 — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a malicious HTTP/2 server to exhaust memory on the client host and cause a denial of service.

Mint.HTTP2 enforces the client's max_header_list_size setting only on the compressed size of an inbound header block, while RFC 9113 section 6.5.2 defines the limit on the decoded header list. An HPACK indexed field costs one byte on the wire and decodes to a dynamic table entry of up to 4 KB, and join_cookie_headers/1 in lib/mint/http2.ex copies every cookie value of a response into one new binary. A header block under the default 256 KB wire limit therefore makes the client allocate about 1 GB for a single response, and several such responses in one delivery exhaust the memory of the process that owns the connection or of the whole VM.

This issue affects mint: from 1.1.0 before 1.10.2.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 29, 2026

Advisory Details (5)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit c7895cb02219 (elixir-mint/mint)

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

https://github.com/elixir-mint/mint/commit/c7895cb022196c77ec35570c8e873a84393ff4b8
github_commit

commit 8e0e04680476 (elixir-mint/mint)

Fix landed in elixir-mint/mint commit 8e0e04680476 — awaiting tagged release

https://github.com/elixir-mint/mint/commit/8e0e04680476f90f9f68db4dfeabcbe66dabfc4d
generic

Vulnerability Database - OSV

https://osv.dev/vulnerability/EEF-CVE-2026-91043
generic🟡 PoC Available

CVE-2026-91043

https://cna.erlef.org/cves/CVE-2026-91043.html
github Patch Available🟡 PoC Available

HPACK-indexed cookie fields in Mint HTTP/2 responses bypass max_header_list_size and exhaust client memory · Advisory · elixir-mint/mint · GitHub

https://github.com/elixir-mint/mint/security/advisories/GHSA-9x8p-qrf4-jq7g

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
mint1.1.0 ... 1.9.3 (22 versions)1.10.2—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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.

  1. 2026-10-04 01:03 UTCEG score recompute
  2. 2026-10-03 00:48 UTCEG score recompute
  3. 2026-10-02 00:32 UTCEG score recompute
  4. 2026-10-01 19:51 UTCEPSS rescore
  5. 2026-10-01 00:14 UTCEG score recompute
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-29 23:46 UTCEG score recompute
  8. 2026-09-29 11:32 UTCEG score recompute
  9. 2026-09-29 10:42 UTCEG score recompute
  10. 2026-09-29 02:52 UTCEG score recompute
  11. 2026-09-28 14:25 UTCEG score recompute
  12. 2026-09-28 13:43 UTCEG score recompute
  13. 2026-09-28 12:31 UTCEG score recompute
  14. 2026-09-28 11:22 UTCEG score recompute
  15. 2026-09-28 11:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-91043?
CVE-2026-91043 is a high vulnerability published on September 28, 2026. Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a malicious HTTP/2 server to exhaust memory on the client host and cause a denial of service. Mint.HTTP2 enforces the client's maxheaderlistsize setting only on the compressed size of an inbound header…
When was CVE-2026-91043 disclosed?
CVE-2026-91043 was first published on September 28, 2026, with the most recent update on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91043 actively exploited?
CVE-2026-91043 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-91043?
CVE-2026-91043 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-91043?
A fix for CVE-2026-91043 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-91043

Explore →

Is Your Infrastructure Affected by CVE-2026-91043?

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