CVE-2026-116269: MIME::Field::ParamVal versions before 5.521 for Perl turn an RFC 2231 filename with a hyphenated language tag into an empty recommended filename

Published Oct 28, 2026
·
Updated

MIME::Field::ParamVal versions before 5.521 for Perl turn an RFC 2231 filename with a hyphenated language tag into an empty recommended filename.

A parameter such as filename=utf-8'en-US'payload.exe is converted to an encoded word with the language tag appended to the charset. The decoder strips the language suffix only when it is a single word, so it cannot resolve the charset UTF-8EN-US and returns an empty string. The recommendedfilename() method returns that empty string rather than falling back to the name parameter.

Other mail readers return payload.exe. A remote sender can get an attachment past a policy that checks file extensions on the recommended filename.

Affected Software

1 affected component
cpan/MIME::Field::ParamVal<5.521

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MIME-tools to a version that resolves this vulnerability.

    Fixed in 5.521

Event History

Oct 28, 2026
CVE Published
via MITRE·05:33 PM
Data Sourced
via MITRE·05:33 PM
RemedyDescriptionWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using MIME::Field::ParamVal before version 5.521 are exposed if they use recommended_filename() to enforce attachment filename-extension policies on remotely supplied email or MIME content.

2

What does an attacker need to send to trigger the problem?

The attacker needs to provide an RFC 2231 filename parameter with a hyphenated language tag, such as filename*=utf-8'en-US'payload.exe. This causes recommended_filename() to return an empty string instead of the supplied filename.

3

Are all attachment filename checks affected?

No. The described bypass applies specifically to policies that check extensions using the recommended filename returned by recommended_filename(). Other mail readers may resolve the same parameter as payload.exe.

4

What can be done before upgrading?

Do not treat an empty recommended filename as safe or as a reason to skip filename-extension enforcement. Ensure attachment handling accounts for the original RFC 2231 filename parameter and rejects or quarantines malformed or unresolved filename encodings.

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