CVE-2026-42504

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated Jun 11, 2026
No patch confirmed yet.
generic

GO-2026-5038 - Go Packages

https://pkg.go.dev/vuln/GO-2026-5038
generic

mime: quadratic complexity in WordDecoder.DecodeHeader · Issue #79217 · golang/go · GitHub

https://go.dev/issue/79217

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-rhel9-operator:17840049142026-07-21redhat
redhatmta/mta-cli-rhel9:17842113782026-07-21redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842961272026-07-20redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842957672026-07-20redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842962032026-07-20redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842960332026-07-20redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842476102026-07-20redhat
redhatweb-terminal/web-terminal-exec-rhel9:17842961142026-07-20redhat
redhatrhdh/rhdh-rhel9-operator:17842105752026-07-20redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatgolang1-26-main-1.26.4-2.hum12026-06-04redhat
redhatgolang1-25-main-1.25.11-2.hum12026-06-04redhat

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 rangeFixed inDependents
stdlib1.26.4

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 78× 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.

Showing the most recent 100 of 184 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42504?
CVE-2026-42504 is a high vulnerability published on June 2, 2026. Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU.
When was CVE-2026-42504 disclosed?
CVE-2026-42504 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42504 actively exploited?
CVE-2026-42504 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.8% of all scored CVEs.
What is the CVSS score of CVE-2026-42504?
CVE-2026-42504 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-42504?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42504, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-42504?

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