Live › vulnerability › CVE-2026-116270
Go to dashboardMIME::Words before 5.521 appends the whole input string to an error variable for each malformed "=?" marker, so a crafted header multiplies its size. From 5.518 onward MIME::Parser runs this on every multipart boundary, so one Content-Type header from a remote sender can exhaust the parsing process's memory.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Applications that parse inbound email or multipart content with MIME::Parser from MIME-Tools 5.518 or later, where attacker-controlled Content-Type headers reach the parser. Systems that only generate mail or never parse untrusted MIME input are unlikely to be exposed.
No product ranges from the sources yet.
perl -MMIME::Words -e 'print $MIME::Words::VERSION' or cpan -l | grep MIME-Tools to find the installed MIME::Words version.grep -r "MIME::Parser" . in the application source.5.521 or later (distributed with MIME-Tools).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116270")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.