CVE-2026-94440: Memory limit bypass when parsing MIME headers in net/textproto, mime/multipart

Published Oct 8, 2026
·
Updated

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.

Affected Software

1 affected component
Google Go

Event History

Oct 8, 2026
CVE Published
via MITRE·10:53 PM
Data Sourced
via MITRE·10:53 PM
DescriptionWeakness

Frequently Asked Questions

1

When can this memory-limit bypass occur?

It can occur while parsing a multipart form when the remaining memory limit at the start of a part is less than 400 bytes. In that condition, MIME header parsing can read an arbitrarily long line into memory despite the limit.

2

What is the practical impact for affected applications?

An affected application may allocate memory for an arbitrarily long MIME header line while processing multipart form data. This can defeat the application's expected memory limit for that parsing operation.

3

What input would an attacker need to provide?

The attacker would need multipart form data containing a part reached when fewer than 400 bytes remain under the parser's memory limit, with an arbitrarily long line in its MIME headers.

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