CVE-2026-92103

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a malicious HTTP/2 server to make the client hold up to about 16 MiB per connection in frames it should reject, consuming client memory.

Mint.HTTP2.Frame.decode_next/2 in lib/mint/http2/frame.ex compares a frame with the client's max_frame_size (16,384 bytes by default) only once the whole declared payload has arrived. Until then it returns :more, and Mint.HTTP2 keeps every received byte in the connection buffer. A server can declare a frame length of up to 16,777,215 bytes and withhold the last byte, keeping roughly 1,024 times the advertised limit buffered for as long as the connection stays open. The server has to send every byte the client buffers, so there is no amplification, and the buffer stops at the 24-bit frame length limit.

This issue affects mint: from 0.1.0 before 1.10.2.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 20252ca85065 (elixir-mint/mint)

Fix landed in elixir-mint/mint commit 20252ca85065 — awaiting tagged release

https://github.com/elixir-mint/mint/commit/20252ca85065f4d1092aed9ee4ed21841a507dfe
github_commit

commit 596ca4304504 (elixir-mint/mint)

Fix landed in elixir-mint/mint commit 596ca4304504 — awaiting tagged release

https://github.com/elixir-mint/mint/commit/596ca4304504be68939c4929e0831557097962b8
generic

Vulnerability Database - OSV

https://osv.dev/vulnerability/EEF-CVE-2026-92103
generic🟡 PoC Available

CVE-2026-92103

https://cna.erlef.org/cves/CVE-2026-92103.html
github Patch Available🟡 PoC Available

Mint HTTP/2 client buffers oversized frames to ~16 MiB before enforcing max_frame_size, enabling remote memory exhaustion · Advisory · elixir-mint/mint · GitHub

Affected: 1.11.0

https://github.com/elixir-mint/mint/security/advisories/GHSA-q95c-ccq6-j5j6

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
mint0.1.0 ... 1.9.3 (29 versions)1.10.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 23:12 UTCEG score recompute
  2. 2026-10-02 20:59 UTCEG score recompute
  3. 2026-10-01 19:51 UTCEPSS rescore
  4. 2026-09-30 16:26 UTCEG score recompute
  5. 2026-09-30 15:30 UTCEG score recompute
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-30 13:47 UTCEG score recompute
  8. 2026-09-29 11:32 UTCEG score recompute
  9. 2026-09-29 10:42 UTCEG score recompute
  10. 2026-09-28 12:31 UTCEG score recompute
  11. 2026-09-28 11:22 UTCEG score recompute
  12. 2026-09-28 11:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92103?
CVE-2026-92103 is a medium vulnerability published on September 28, 2026. Allocation of Resources Without Limits or Throttling vulnerability in elixir-mint mint allows a malicious HTTP/2 server to make the client hold up to about 16 MiB per connection in frames it should reject, consuming client memory. Mint.HTTP2.Frame.decodenext/2 in lib/mint/http2/frame.ex compares a…
When was CVE-2026-92103 disclosed?
CVE-2026-92103 was first published on September 28, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92103 actively exploited?
CVE-2026-92103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92103?
CVE-2026-92103 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92103?
A fix for CVE-2026-92103 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92103

Explore →

Is Your Infrastructure Affected by CVE-2026-92103?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.