HPACK-indexed cookie fields in Mint HTTP/2 responses bypass max_header_list_size and exhaust client memory
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: elixir-mint mint 1.10.2, 65a0d61c9eab6b0dedac809de7212515bf506250, c7895cb022196c77ec35570c8e873a84393ff4b8.
Low priority for now. Upgrade to elixir-mint mint 1.10.2, 65a0d61c9eab6b0dedac809de7212515bf506250, c7895cb022196c77ec35570c8e873a84393ff4b8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 28, 2026
- Updated
- Sep 29, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- CWE-770
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · EEF
- 8.2
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.
elixir-mint mint
- 1.1.0 and later · before 1.10.2affected · semver
- 8e0e04680476f90f9f68db4dfeabcbe66dabfc4d and lateraffected · gitfixed in c7895cb022196c77ec35570c8e873a84393ff4b8, 65a0d61c9eab6b0dedac809de7212515bf506250
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Hex | mint | from 1.1.0 · before 1.10.2 | 1.10.2 |
Same product
elixir-mint: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-56810mint buffers an entire chunked response chunk in memory in Mint.HTTP1.decode_body/534Monitor
- CVE-2026-82728Unbounded HTTP/1 status-line and chunk-extension buffering in Mint causes memory-exhaustion DoS32Monitor
- CVE-2026-58229Unbounded HTTP/1 response-header and chunked-trailer accumulation in Mint causes memory-exhaustion DoS32Monitor
- CVE-2026-49754HTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation32Monitor
- CVE-2026-48862Unbounded conn.streams growth in Mint HTTP/2 client via unenforced PUSH_PROMISE concurrency32Monitor
- CVE-2026-94194Mint HTTP/1 client applies chunked framing when chunked is not the final transfer coding, enabling response smuggling through intermediaries25Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| elixir-mint mint | 1.10.2 | Vendor (CNA) |
| elixir-mint mint | 65a0d61c9eab6b0dedac809de7212515bf506250 | Vendor (CNA) |
| elixir-mint mint | c7895cb022196c77ec35570c8e873a84393ff4b8 | Vendor (CNA) |
| Hex:mint | 1.10.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 16, 2026+18 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Eric Meadows-Jönssonfinder
- Andrea Leopardiremediation reviewer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-5681084 days apartmint buffers an entire chunked response chunk in memory in Mint.HTTP1.decode_body/534Monitor
- CVE-2026-8272824 days apartUnbounded HTTP/1 status-line and chunk-extension buffering in Mint causes memory-exhaustion DoS32Monitor
- CVE-2026-5822976 days apartUnbounded HTTP/1 response-header and chunked-trailer accumulation in Mint causes memory-exhaustion DoS32Monitor
- CVE-2026-48862118 days apartUnbounded conn.streams growth in Mint HTTP/2 client via unenforced PUSH_PROMISE concurrency32Monitor
- CVE-2026-49754118 days apartHTTP/2 CONTINUATION flood in Mint client via unbounded header-block accumulation32Monitor
- CVE-2026-921030 days apartMint HTTP/2 client buffers oversized frames up to 16 MiB before enforcing max_frame_size25Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
- SSVC exploitation— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/elixir-mint/mint/commit/65a0d61c9eab6b0dedac809de7212515bf506250
- github.com/elixir-mint/mint/commit/8e0e04680476f90f9f68db4dfeabcbe66dabfc4d
- github.com/elixir-mint/mint/commit/c7895cb022196c77ec35570c8e873a84393ff4b8
- github.com/elixir-mint/mint/security/advisories/GHSA-9x8p-qrf4-jq7g
- osv.dev/vulnerability/EEF-CVE-2026-91043
Vendor advisories and official records. Exploit/PoC links are deliberately left out.