CVE-2026-116266

MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous.

The multipart_boundary() method decodes RFC 2047 encoded words anywhere in the boundary, but the ambiguity check only fires when the whole value is one encoded word. A boundary such as abc=?us-ascii?Q?def?= is used as abcdef, and ambiguous_content() returns false.

Encoded words are not allowed in parameters, so other mail readers split the message on the literal value. A remote sender can hide an attachment from a filter that relies on ambiguous_content() while the recipient's mail client shows it.

Analysis

AI-generated

Technical impact

The MIME::Head module in Perl’s MIME-tools parses a multipart boundary that contains an RFC 2047 encoded word and decodes the encoded segment as plain text while the ambiguous_content() check is only triggered when an entire boundary is encoded. This results in a boundary such as abc=?us-ascii?Q?def?= being interpreted as abcdef, with the ambiguous_content flag reported as false. The flaw therefore allows a crafted email to conceal an attachment from mail‑filtering tools that depend on ambiguous_content(), causing the recipient’s client to display the attachment as normal.

Affected Systems

This issue affects MIME-tools versions 5.518 through 5.520, which are included in many Perl‑based mail clients and server‑side filtering utilities that parse MIME headers. Any deployment that incorporates the vulnerable library, regardless of whether it is a client or a proxy filter, is exposed to the crafted boundary attack.

Risk and Exploitability

The EPSS score of <1 % indicates a low but non‑zero likelihood of exploitation, and the CVSS base score of 5.3 reflects moderate severity. Based on the description, it is inferred that an attacker can craft a message containing an RFC 2047 encoded word within a multipart boundary, leading to a remote exploitation scenario that does not require local privileges or elevated rights. Because the flaw is triggered by a standard email format, the attack vector is simply a malicious message sent to a vulnerable system. Although the vulnerability is not currently listed in CISA’s KEV catalog, mail filtering solutions that rely solely on ambiguous_content() may be bypassed, resulting in potential delivery of malicious attachments.

Remediation

Vendor Solution

Upgrade to MIME-tools 5.521 or later.


OpenCVE Recommended Actions

  • Apply the official vendor update—upgrade MIME-tools to version 5.521 or later, which eliminates the incorrect boundary decoding and fixes the ambiguous_content logic (addressing CWE‑115 and CWE‑436).
  • Insert an explicit validation rule in your mail‑processing pipeline that rejects any multipart boundary containing RFC 2047 encoded words or other disallowed characters; this guards against the improper validation weakness (CWE‑115).
  • Enforce a secondary boundary check that flags any message where ambiguous_content() is false but the boundary value differs from the raw header; this mitigates the risk that a mis‑parsed boundary value (CWE‑436) propagates into downstream processing.

Generated by OpenCVE AI on October 30, 2026 at 14:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-115
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Perl
Perl mime::head
Vendors & Products Perl
Perl mime::head
Type Values Removed Values Added
Description MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous. The multipart_boundary() method decodes RFC 2047 encoded words anywhere in the boundary, but the ambiguity check only fires when the whole value is one encoded word. A boundary such as abc=?us-ascii?Q?def?= is used as abcdef, and ambiguous_content() returns false. Encoded words are not allowed in parameters, so other mail readers split the message on the literal value. A remote sender can hide an attachment from a filter that relies on ambiguous_content() while the recipient's mail client shows it.
Title MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous
Weaknesses CWE-436
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 5, 2026, 8:21 PM
Reserved
Oct 25, 2026, 6:05 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 6:17 PM
Modified
Nov 5, 2026, 9:18 PM
Severity
Moderate
Public date
Oct 28, 2026, 5:32 PM