CVE-2026-39414

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-20602 (ENISA EUVD) · GHSA-h749-fxx7-pwpg (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

MinIO is a high-performance object storage system. From RELEASE.2018-08-18T03-49-57Z to before RELEASE.2025-12-20T04-58-37Z, MinIO's S3 Select feature is vulnerable to memory exhaustion when processing CSV files containing lines longer than available memory. The CSV reader's nextSplit() function calls bufio.Reader.ReadBytes('\n') with no size limit, buffering the entire input in memory until a newline is found. A CSV file with no newline characters causes the entire contents to be read into a single allocation, leading to an OOM crash of the MinIO server process. This is exploitable by any authenticated user with s3:PutObject and s3:GetObject permissions. The attack is especially practical when combined with compression: a ~2 MB gzip-compressed CSV can decompress to gigabytes of data without newlines, allowing a small upload to cause large memory consumption on the server. However, compression is not required — a sufficiently large uncompressed CSV with no newlines triggers the same issue.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
41st
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.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

April 8, 2026

Last Modified

July 24, 2026

Advisory Details (3)

Auto-updated Jun 15, 2026
Fix referenced — no release confirmed yet. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

DoS via Unbounded Memory Allocation in S3 Select CSV Parsing · Advisory · minio/minio · GitHub

https://github.com/minio/minio/security/advisories/GHSA-h749-fxx7-pwpg
GitHub pull request

Concurrent CSV parsing and reduce S3 select allocations

Fix merged in minio/minio PR #8200 on 2019-09-13 — awaiting tagged release

https://github.com/minio/minio/pull/8200
Web page

Upgrade from open-source MinIO | MinIO AIStor Documentation

https://docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/community-edition

Vendor Advisories for CVE-2026-39414(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/minio/minio—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/minio/minio—
  • 0.0.0-20180815103019-7c14cdb60e53 on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 38× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 99 of 222 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 123 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-25 14:31 UTCEG score recompute
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  9. 2026-10-23 02:51 UTCEG score recompute
  10. 2026-10-23 02:51 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  16. 2026-10-18 03:43 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  18. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-10-12 16:10 UTCEG score recompute
  24. 2026-10-11 19:52 UTCEG score recompute
  25. 2026-10-11 17:06 UTCEG score recompute
Show 74 more
  1. 2026-10-11 14:32 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  3. 2026-10-10 21:33 UTCOSV refresh
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  14. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  17. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  18. 2026-09-21 09:19 UTCOSV refresh
  19. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  26. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  27. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  28. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  29. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  30. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  31. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  32. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  33. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  34. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-02 07:44 UTCOSV refresh
  36. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  49. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-08-16 07:17 UTCEG score recompute
  52. 2026-08-16 07:17 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  53. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-08-14 05:14 UTCEG score recompute
  56. 2026-08-14 05:14 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  57. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-08-13 00:03 UTCEG score recompute
  59. 2026-08-13 00:03 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  60. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-08-12 01:34 UTCEG score recompute
  62. 2026-08-12 01:34 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  63. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-08-11 03:05 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  65. 2026-08-10 03:11 UTCEG score recompute
  66. 2026-08-10 03:11 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  67. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-08-09 04:42 UTCEG score recompute
  69. 2026-08-09 04:42 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  70. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  71. 2026-08-07 14:36 UTCEG score recompute
  72. 2026-08-07 14:36 UTCGHSA enrichmentGHSA-h749-fxx7-pwpg · GitHub severity HIGH
  73. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  74. 2026-08-05 23:50 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-39414?
CVE-2026-39414 is a medium-severity vulnerability; its CVE record was published on April 8, 2026. MinIO is a high-performance object storage system. From RELEASE.2018-08-18T03-49-57Z to before RELEASE.2025-12-20T04-58-37Z, MinIO's S3 Select feature is vulnerable to memory exhaustion when processing CSV files containing lines longer than available memory. The CSV reader's nextSplit() function…
When was the CVE record for CVE-2026-39414 published?
The CVE record for CVE-2026-39414 was published on April 8, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-39414 actively exploited?
CVE-2026-39414 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39414?
CVE-2026-39414 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-39414?
A fix for CVE-2026-39414 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-39414 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-39414?

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

Book a Demo →Browse All CVEs