Skip to main content
Mallory
High

Excessive CPU consumption in Go mime.WordDecoder.DecodeHeader

IdentifiersCVE-2026-42504CWE-407· Inefficient Algorithmic Complexity

CVE-2026-42504 is a denial-of-service vulnerability in Go's mime package affecting mime.WordDecoder.DecodeHeader. According to the provided content, the vulnerable behavior is a quadratic-complexity condition triggered while decoding a maliciously crafted MIME header containing many invalid encoded-words. An attacker can supply specially constructed header input that causes DecodeHeader to perform excessive processing, leading to disproportionate CPU consumption. The issue was addressed in Go 1.26.4 and Go 1.25.11, where the MIME decoder was updated to better handle this malformed-input case.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can drive excessive CPU utilization in applications that parse attacker-controlled MIME headers using mime.WordDecoder.DecodeHeader. The practical impact is resource exhaustion and potential denial of service, especially in services that process large volumes of untrusted email or MIME-like header data.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by avoiding or limiting processing of untrusted MIME headers with mime.WordDecoder.DecodeHeader, enforcing strict header size and complexity limits, rejecting malformed headers with excessive encoded-word usage, and applying request/message rate limiting and CPU/resource controls to reduce denial-of-service impact. Specific vendor-provided mitigations beyond upgrading were not provided in the content.

Remediation

Patch, then assume compromise.

Upgrade to a fixed Go release. The provided content states that the issue is fixed in Go 1.26.4 and Go 1.25.11. Rebuild and redeploy affected applications against one of these patched versions or a later release.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.