Quadratic complexity in WordDecoder.DecodeHeader in mime
Summary
| CVE | CVE-2026-42504 |
|---|---|
| State | PUBLISHED |
| Assigner | Go |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-06-02 23:16:37 UTC |
| Updated | 2026-06-03 16:16:30 UTC |
| Description | Decoding a maliciously-crafted MIME header containing many invalid encoded-words can consume excessive CPU. |
Risk And Classification
Primary CVSS: v3.1 7.5 HIGH from ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.000180000 probability, percentile 0.047770000 (date 2026-06-03)
Problem Types: CWE-407 | CWE-407: Inefficient Algorithmic Complexity | CWE-407 CWE-407 Inefficient Algorithmic Complexity
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | ADP | DECLARED | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| 3.1 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | Secondary | 7.5 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Go Standard Library | Mime | affected 1.25.11 semver | Not specified |
| CNA | Go Standard Library | Mime | affected 1.26.0-0 1.26.4 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| go.dev/cl/774481 | [email protected] | go.dev | |
| go.dev/issue/79217 | [email protected] | go.dev | |
| groups.google.com/g/golang-announce/c/tKs3rmcBcKw | [email protected] | groups.google.com | |
| pkg.go.dev/vuln/GO-2026-5038 | [email protected] | pkg.go.dev | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Vendor Comments And Credit
Discovery Credit
CNA: p4p3r (https://hackerone.com/p4p3r_hak) (en)
There are currently no legacy QID mappings associated with this CVE.