CVE-2026-116265

MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations.

The boundary ambiguity checks look only at a plain boundary= parameter, and a boundary split into RFC 2231 sections (boundary*0=, boundary*1= and so on) is joined after they have run. A repeated section number is concatenated rather than reported as a duplicate. From version 5.518, an encoded word or trailing whitespace in such a boundary also goes unflagged, although multipart_boundary() decodes or strips it.

A remote sender can make MIME::Parser split a message on a different boundary than other mail readers, hiding an attachment from a filter that relies on ambiguous_content() while the recipient's mail client shows it.

Analysis

AI-generated

Technical impact

MIME::Field::ParamVal versions before 5.521 fail to detect an ambiguous multipart boundary when the boundary is expressed as RFC 2231 continuations or contains encoded words and trailing whitespace. This flaw allows a crafting of an email where the MIME parser splits the message on a different boundary than other receivers, thereby hiding an attachment from a security filter that relies on the ambiguous_content() check while still displaying it in the recipient’s mail client. The impact is the potential delivery of malicious attachments or hidden content to a victim without the filtering system detecting it.

Affected Systems

The vulnerability affects the MIME-tools Perl library, specifically the MIME::Field::ParamVal module, in all releases prior to 5.521. Versions 5.518 and earlier also fail to flag encoded words or trailing whitespace in boundary parameters, and users of 5.519 and 5.520 are similarly impacted. The issue is corrected in 5.521 and later releases of MIME-tools.

Risk and Exploitability

The flaw is exploitable remotely via an email message sent from a non‑trusted source. No local privilege escalation or arbitrary code execution is required; an attacker merely needs to craft the boundary parameters in the message. The EPSS score is below 1%, indicating a very low but non‑zero likelihood of exploitation. The CVSS score of 5.3 reflects a moderate severity that affects confidentiality, integrity, and availability by allowing attachment concealment. The vulnerability is not listed in the CISA KEV catalog. Because the flaw can lead to successful content injection and bypass of security controls, the risk remains significant, especially in environments that rely on older MIME-tools for email filtering. The identified weakness corresponds to CWE-179 and CWE-436. The attack vector is network‑based, and the fragility exists in the parsing logic of the library.

Remediation

Vendor Solution

Upgrade to MIME-tools 5.521 or later.


OpenCVE Recommended Actions

  • Upgrade the MIME-tools Perl library to version 5.521 or later, which implements correct boundary ambiguity checks and rejects duplicate or malformed boundary continuations.
  • If an immediate upgrade is not possible, audit existing installations of MIME::Field::ParamVal to ensure they are not older than 5.521 before processing untrusted messages, and consider isolating email parsing to a hardened subsystem or container that can be refreshed independently.
  • For environments that require compatibility with older MIME-tools, disable reliance on the ambiguous_content() check and instead implement a stricter boundary validation routine that rejects RFC 2231 continuations containing duplicate indices or whitespace in the boundary value.

Generated by OpenCVE AI on October 30, 2026 at 13:42 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-179
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::field::paramval
Vendors & Products Perl
Perl mime::field::paramval
Type Values Removed Values Added
Description MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations. The boundary ambiguity checks look only at a plain boundary= parameter, and a boundary split into RFC 2231 sections (boundary*0=, boundary*1= and so on) is joined after they have run. A repeated section number is concatenated rather than reported as a duplicate. From version 5.518, an encoded word or trailing whitespace in such a boundary also goes unflagged, although multipart_boundary() decodes or strips it. A remote sender can make MIME::Parser split a message on a different boundary than other mail readers, hiding an attachment from a filter that relies on ambiguous_content() while the recipient's mail client shows it.
Title MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations
Weaknesses CWE-436
References
Weaknesses
  • CWE-179

    Incorrect Behavior Order: Early Validation

  • CWE-436

    Interpretation Conflict

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 5, 2026, 8:18 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