CVE-2026-42504: Quadratic complexity in WordDecoder.DecodeHeader in mime

Published Jun 2, 2026
·
Updated

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

Other sources

Quadratic complexity in WordDecoder.DecodeHeader in mime

Microsoft

Affected Software

5 affected componentsFixes available
go mime package
Microsoft azl3 golang 1.26.3-1
Microsoft azl3 golang 1.26.3-1<1.26.4-1
1.26.4-1
Microsoft azl3 golang 1.26.4-3<1.26.4-1
1.26.4-1
Microsoft azl3 golang 1.25.11-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.26.4-1

Event History

Jun 2, 2026
CVE Published
via MITRE·10:01 PM
Data Sourced
via MITRE·10:01 PM
DescriptionWeakness
Data Sourced
via Red Hat·11:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeakness
Jun 5, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
Affected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Updated
via Microsoft·08:02 AM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-42504?

The severity of CVE-2026-42504 is rated as high with a CVSS score of 7.5.

2

What are the potential impacts of CVE-2026-42504?

CVE-2026-42504 can lead to excessive CPU consumption when decoding a maliciously-crafted MIME header.

3

How do I fix CVE-2026-42504?

To fix CVE-2026-42504, it is recommended to update to the latest version of the Go mime package that addresses this issue.

4

What versions of the Go mime package are affected by CVE-2026-42504?

CVE-2026-42504 affects versions of the Go mime package before the patch is applied in the update.

5

Is there a workaround for CVE-2026-42504?

Currently, there are no specific workarounds for CVE-2026-42504 other than updating to the fixed version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203