VulnerabilityPublished 28 Sep 2026Updated 30 Sep 2026

CVE-2026-94194: mint · HTTP Request/Response Smuggling

Affects mintSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.10.2 when convenient.

Data as of 12 Nov 2026, 23:25 UTC

CVSS 4.0 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.10.2

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade mint to 1.10.2.

Affected software

Product	Affected	Fixed in
elixir-mintmint	Affected >=0.1.0 <1.10.2	Fixed in 1.10.2
elixir-mintmint	Affected ≥ 60089586ec7adc9fddb09f69a2f5919ba9ac7f33, < 2ec8b696b5475ecbdaa87c0098957bca339e17c0	Fixed in–
Hexmint`pkg:hex/mint`Other threats	Affected >=0.1.0 <1.10.2	Fixed in 1.10.2

CPE configurations (1)

cpe:2.3:a:elixir-mint:mint:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in mint version 1.10.2 and later. Users should upgrade to version 1.10.2 or newer to address this vulnerability. No vendor advisory content was provided to indicate alternative mitigations or temporary workarounds. Patch status is confirmed by the version range affected and fixed stated in the description.

Description

CVE-2026-94194 is a medium severity vulnerability in the elixir-mint mint HTTP client library. It involves inconsistent interpretation of HTTP/1 responses, specifically in handling Transfer-Encoding headers with multiple codings and connection persistence after HTTP/1.0 responses. This can lead to HTTP request/response smuggling where a malicious HTTP/1 server desynchronizes an intermediary and the Mint client on a pooled connection, causing response poisoning for subsequent requests sharing the connection.

Impact

An attacker controlling an HTTP/1 server can exploit this vulnerability to desynchronize the Mint client and intermediaries on pooled connections. This can result in response poisoning, where the client receives incorrect or malicious responses to subsequent requests, potentially leading to data leakage, request forgery, or other security issues related to HTTP request/response smuggling.

Summary

The vulnerability arises because the message_body/1 function in lib/mint/http1.ex incorrectly selects chunked framing whenever 'chunked' is the first coding in the Transfer-Encoding header, contrary to RFC 9112 section 6.3, which requires chunked framing only when 'chunked' is the final coding. For example, a response with 'Transfer-Encoding: chunked, gzip' is handled differently by Mint and intermediaries, leading to desynchronization. Additionally, Mint keeps connections open after HTTP/1.0 responses with Transfer-Encoding and Connection: keep-alive, violating RFC 9112 section 6.1, which mandates closing such connections. These protocol deviations allow a malicious HTTP/1 server to poison responses to subsequent requests on the same connection, enabling HTTP request/response smuggling attacks. This affects all versions of mint from 0.1.0 up to but not including 1.10.2.

CWE-444Inconsistent Interpretation of HTTP Requests (HTTP Request Smuggling) (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 5 Oct 2026, 20:36 UTC

WeaknessesCWE-444

Technical details

References

Community reviews

Related threats