Answer in brief
CVE-2026-82729 records a Medium severity (CVSS 6.3) vulnerability in Quadratic chunk-size parsing in Mint.HTTP1.Parse allows CPU-exhaustion DoS. The current sources do not mark it as known exploited. The current feed maps elixir-mint/elixir-mint/mint (generic), elixir-mint/mint (generic), elixir-mint/mint (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps elixir-mint/elixir-mint/mint (generic), elixir-mint/mint (generic), elixir-mint/mint (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| elixir-mint/elixir-mint/mintgeneric | >=fc7d16538db7e40b56ed489f08683225cb0197fa <bd2a4e7513594997c140cfef9fe0e968712fb588 | bd2a4e7513594997c140cfef9fe0e968712fb588 |
| elixir-mint/mintgeneric | >=fc7d16538db7e40b56ed489f08683225cb0197fa <bd2a4e7513594997c140cfef9fe0e968712fb588 | bd2a4e7513594997c140cfef9fe0e968712fb588 |
| elixir-mint/mintgeneric | >=1.9.3 <1.10.0 | 1.10.0 |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
Inefficient Algorithmic Complexity vulnerability in elixir-mint mint allows a remote HTTP server to exhaust CPU on the client host and cause a denial of service. parse_hex_prefix/2 in lib/mint/http1/parse.ex folds each hex digit of a chunked response's chunk-size field into an arbitrary-precision accumulator with acc * 16 + digit and imposes no limit on the digit count. Because the accumulator grows without bound, the multiplication is not constant time and one pass over N digits costs O(N squared). handle_data/2 prepends conn.buffer and re-parses from the start on every socket message, so a server that dribbles the digits out in small packets makes the client pay that cost repeatedly. A run of roughly 512,000 hex digits costs over ten seconds of CPU in a single pass, measured on stock defaults. The parser reaches this state after a valid status line and a complete, valid header section, so an intermediary inspecting only headers sees an ordinary 200 response. This issue affects mint: from 1.9.3 before 1.10.0.
Quoted source text, attributed separately from HOL analysis.