Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-82672Published 2026-09-19

CVE-2026-82672 — elixir-mint mint

medium (derived)Public exploit1 PoC repo

As of 2026-09-19, CVE-2026-82672 is a Medium-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in elixir-mint mint, CVSS v4.0 6.3, EPSS 0.3% (23.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-82672 as of 2026-09-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
6.3/10Medium (derived)
EPSS
0.3%Higher than 23.0% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
6.1/10Threadlinqs triage score
Published
CVSS v4.0 6.3 (Medium, derived from score) · EPSS 0.3% (higher than 23.0% of all scored CVEs) · Priority 6.1/10 · Published 2026-09-19

Last updated:

What is CVE-2026-82672?

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') vulnerability in elixir-mint mint allows a malicious HTTP/1 server to desynchronize a strict intermediary and the Mint client on a pooled connection, enabling response-queue poisoning against subsequent requests that share the connection. Mint.HTTP1.Parse.chunk_size/1 in lib/mint/http1/parse.ex stops at the first non-hexadecimal byte of a chunked response's chunk-size line and returns the remainder unexamined. Mint.HTTP1.decode_body/5 in lib/mint/http1.ex then discards every byte up to the CRLF with Parse.ignore_until_crlf/1, so the accepted grammar is a run of hex digits followed by arbitrary bytes, where RFC 9112 permits only a ;-introduced chunk extension. Lines such as 5ZZZZZ and 5 9 are accepted as chunk size 5, and 0ZZZZ is accepted as the terminating chunk that ends the message body. An RFC-strict intermediary rejects such a line while Mint accepts it, so the two disagree on chunk boundaries and on where the response ends. This issue affects mint: from 0.1.0 before 1.10.1.

The record classifies CVE-2026-82672 under weakness class CWE-444. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 16 days ago.

Severity and exploitation probability

CVSS v4.0 base score
6.3 — Medium (derived from score)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS (FIRST)
0.3% probability of exploitation in the next 30 days, higher than 23.0% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
6.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-09-19

Is CVE-2026-82672 being exploited?

Weaponised exploit code for CVE-2026-82672 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 44 in the Threadlinqs vulnerability feed.

Affected products and versions

  • elixir-mint: mint

How to fix CVE-2026-82672

No vendor patch reference has been recorded for CVE-2026-82672 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-82672

No threat campaign in the Threadlinqs corpus currently references CVE-2026-82672, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references