CVE-2026-120287

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-127132 (ENISA EUVD)Source: ENISA EUVD

6.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Allocation of Resources Without Limits or Throttling vulnerability in Plug.Parsers.MULTIPART in elixir-plug plug allows an unauthenticated remote attacker to exhaust memory via a multipart request body built from parts without headers, or from header lines without a name and a value. The parser charges the :length limit only with the name and value bytes of each part header and the bytes of each part body. The part delimiter, the header separator, and the line endings cost nothing.

In lib/plug/parsers/multipart.ex, Plug.Parsers.MULTIPART.parse_multipart_headers/5 keeps an entry for every part without a content-disposition header, together with its header list, until the whole body is read. A request made of such parts does not reach the limit at any size, and the parser process holds a multiple of the request size in memory until parsing completes. Any endpoint that uses Plug.Parsers with the :multipart parser is reachable.

This issue affects plug: from 1.13.0 before 1.20.4.

CVSS
6.9
EG Score
6.9MEDIUMmedium confidence
EG Risk
46
EG Risk 46/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity69% × 45%
Impact severity (EG Severity): CVSS 6.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.9): severity, escalated by confirmed exploitation. This CVE's 6.9 is its impact severity (EG Severity), not escalated.

EG Severity
6.9 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 17, 2026

Last Modified

November 20, 2026

Advisory Details (6)

Auto-updated Nov 17, 2026
Patch available. Sources: github, github_commit.
GitHub commit

commit 3d3fb6453236 (elixir-plug/plug)

Fix landed in elixir-plug/plug commit 3d3fb6453236 — awaiting tagged release

https://github.com/elixir-plug/plug/commit/3d3fb645323643935c6c94863c1b3edfd62e2828
GitHub commit

commit 497913f2a6d7 (elixir-plug/plug)

Fix landed in elixir-plug/plug commit 497913f2a6d7 — awaiting tagged release

https://github.com/elixir-plug/plug/commit/497913f2a6d744d693e98e96c5b9c6d88c265695
GitHub commit

commit e06acbd3d381 (elixir-plug/plug)

Fix landed in elixir-plug/plug commit e06acbd3d381 — awaiting tagged release

https://github.com/elixir-plug/plug/commit/e06acbd3d381931f23cbde7d763136c9ccb091ac
Web page

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-120287
GitHub advisoryMentions a patch (unverified)

Plug.Parsers.MULTIPART does not charge all consumed multipart bytes against `:length`, allowing unbounded part accumulation and memory exhaustion · Advisory · elixir-plug/plug · GitHub

https://github.com/elixir-plug/plug/security/advisories/GHSA-qj4r-jh2r-rw3f

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
plug1.13.0 ... 1.20.3 (45 versions)1.20.4 (one range)—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  3. 2026-11-20 06:28 UTCEchelonGraph re-scored
  4. 2026-11-20 06:06 UTCEchelonGraph re-scored
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-11-19 07:16 UTCEchelonGraph re-scored
  7. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  8. 2026-11-17 18:03 UTCENISA EUVD ID recordedEUVD-2026-127132 · Source: ENISA EUVD
  9. 2026-11-17 17:30 UTCEchelonGraph re-scored
  10. 2026-11-17 16:58 UTCEchelonGraph re-scoredFirst assessed: 6.9 MEDIUM
  11. 2026-11-17 16:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-120287?
CVE-2026-120287 is a medium-severity vulnerability; its CVE record was published on November 17, 2026. Allocation of Resources Without Limits or Throttling vulnerability in Plug.Parsers.MULTIPART in elixir-plug plug allows an unauthenticated remote attacker to exhaust memory via a multipart request body built from parts without headers, or from header lines without a name and a value. The parser…
When was CVE-2026-120287 made public?
CVE-2026-120287 was made public on November 17, 2026: that is the date its CVE record's CNA, Erlang Ecosystem Foundation, gives for when the vulnerability was made public. The CVE record itself was published on November 17, 2026. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-120287 actively exploited?
CVE-2026-120287 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120287?
CVE-2026-120287 has a CVSS base score of 6.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120287?
A fix for CVE-2026-120287 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-120287

Explore →

Is Your Infrastructure Affected by CVE-2026-120287?

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