CVE-2026-116270

MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords

Published Oct 28, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords.

For each "=?" that does not start a complete encoded word, decode_mimewords appends an error message containing the whole input string to $@. A boundary of 8,000 "=?" pairs (16,000 bytes) adds 8,000 copies of itself to $@, about 128 MB.

From version 5.518, MIME::Parser decodes every multipart boundary this way, so a remote sender can exhaust the memory of the parsing process with one Content-Type header.

Analysis

AI-generated

Technical impact

The flaw in MIME::Words allows repeated "=?" sequences that are not part of a complete encoded word to trigger the decoder to append an error message containing the entire input string to the global exception variable $@. A large boundary of 8,000 such pairs, totaling 16,000 bytes, results in 8,000 copies of the input added to $@, consuming roughly 128 megabytes. This memory exhaustion attack can lead to denial of service, as the library does not guard against excessive duplication.

Affected Systems

All Perl installations using MIME::Words prior to version 5.521 are vulnerable. Beginning with MIME::Parser version 5.518, the same decoder is invoked for multipart boundaries, meaning any Perl application that parses MIME content—such as email servers, automated mail handlers, or custom mail processors—will be susceptible when it imports MIME-tools up to 5.520.

Risk and Exploitability

The attack can be performed remotely by an unauthenticated sender who crafts a MIME header containing many incomplete "=?" sequences. The EPSS score is < 1%, the CVSS score is 7.5, and the vulnerability is not listed in CISA KEV, but the single-header exploitation path and large memory impact indicate a high potential for denial of service. The risk remains significant until the libraries are updated or mitigated.

Remediation

Vendor Solution

Upgrade to MIME-tools 5.521 or later.


OpenCVE Recommended Actions

  • Upgrade the MIME-tools package to 5.521 or later on all affected Perl installations.
  • Configure mail or content-processing services to reject MIME headers exceeding a safe size limit or to drop messages with unusually long multipart boundaries.
  • Monitor memory usage of parsing processes and set alerts or automatic restarts for processes that exceed normal thresholds.

Generated by OpenCVE AI on October 30, 2026 at 13:39 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-770
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Important

Type Values Removed Values Added
First Time appeared Perl
Perl mime::words
Vendors & Products Perl
Perl mime::words
Type Values Removed Values Added
Description MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords. For each "=?" that does not start a complete encoded word, decode_mimewords appends an error message containing the whole input string to $@. A boundary of 8,000 "=?" pairs (16,000 bytes) adds 8,000 copies of itself to $@, about 128 MB. From version 5.518, MIME::Parser decodes every multipart boundary this way, so a remote sender can exhaust the memory of the parsing process with one Content-Type header.
Title MIME::Words versions before 5.521 for Perl allow memory exhaustion via repeated "=?" sequences in decode_mimewords
Weaknesses CWE-407
References
Weaknesses
  • CWE-407

    Inefficient Algorithmic Complexity

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Nov 5, 2026, 8:33 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
Important
Public date
Oct 28, 2026, 5:33 PM