CVE-2026-48862
Last modified
CVE-2026-48862 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client via PUSH_PROMISE flooding. In lib/mint/http2.ex, Mint.HTTP2.decode_push_promise_headers_and_add_response/5 inserts a :reserved_remote entry into conn.streams for every promised stream ID. The neighbouring Mint.HTTP2.assert_valid_promised_stream_id/2 only verifies that the promised ID is even and not already present; client_settings.max_concurrent_streams is not consulted at promise time. EPSS estimates a 0.38% chance of exploitation in the next 30 days.
Description
Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint Mint allows attacker-controlled HTTP/2 servers to exhaust memory in a Mint client via PUSH_PROMISE flooding. In lib/mint/http2.ex, Mint.HTTP2.decode_push_promise_headers_and_add_response/5 inserts a :reserved_remote entry into conn.streams for every promised stream ID. The neighbouring Mint.HTTP2.assert_valid_promised_stream_id/2 only verifies that the promised ID is even and not already present; client_settings.max_concurrent_streams is not consulted at promise time. The concurrency cap is only checked when the response HEADERS for the promised stream arrive, so a server that emits PUSH_PROMISE frames and withholds the matching HEADERS never trips that check. HTTP/2 server push is accepted by default (client_settings.enable_push defaults to true). A single long-lived HTTP/2 connection to a hostile server lets that server pin one conn.streams entry per PUSH_PROMISE frame it sends, with no upper bound, until the client process runs out of memory. This issue affects mint: from 0.2.0 before 1.9.0.
Metrics
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
Weakness Enumeration
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-48862?
How severe is CVE-2026-48862?
How do I fix CVE-2026-48862?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-48855Exposure of Sensitive Information to an Unauthorized Actor v…6.5
- CVE-2026-48856Sensitive Data Exposure vulnerability in Erlang OTP inets (h…6.5
- CVE-2026-48858Server-Side Request Forgery (SSRF) vulnerability in Erlang/O…6.5
- CVE-2026-48859Observable Timing Discrepancy vulnerability in Erlang/OTP ss…5.3
- CVE-2026-48860Reliance on IP Address for Authentication vulnerability in E…6.5
- CVE-2026-48861Improper Neutralization of CRLF Sequences ('CRLF Injection')…2.1
- CVE-2026-48863A flaw was found in libsolv. A stack-based buffer overflow v…7.5
- CVE-2026-48864A flaw was found in libsolv. This heap buffer overflow occur…7.8
- CVE-2026-48865Improper Neutralization of Input During Web Page Generation …7.1
- CVE-2026-48866Improper Limitation of a Pathname to a Restricted Directory …9.6
- CVE-2026-48867Unauthenticated Cross Site Scripting (XSS) in Quiz And Surve…7.1
- CVE-2026-48868Unauthenticated Insecure Direct Object References (IDOR) in …7.5
Are you affected by CVE-2026-48862?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
