Live › vulnerability › CVE-2026-116268
Go to dashboardMIME::Field::ParamVal, a Perl module for parsing MIME header parameters, scans each unclosed comment to the end of the header, so parsing takes time quadratic in header length. A crafted message with a long header stalls the parser and ties up CPU; the sources report about 7 seconds for a 40 KB header.
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 written in Perl that parse untrusted MIME messages or Content-Type and Content-Disposition headers with this module, such as mail handlers, upload processors or email-to-web gateways. Systems that never parse attacker-supplied MIME data, or that run a version at or above 5.521, are not exposed.
No product ranges from the sources yet.
perl -MMIME::Field::ParamVal -e 'print $MIME::Field::ParamVal::VERSION' to read the installed versioncpanm --info MIME::Field::ParamVal for the resolved version5.521 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
MIME::Field::ParamVal versions before 5.521 for Perl allow CPU exhaustion via unclosed comments in header parameters.
The comment pattern used to parse Content-Type and Content-Disposition parameters scans from each "(" to the next ")". In a field with no ")", every "(" scans to the end of the header and fails, so parsing takes time quadratic in the header length. The field is parsed again on each attribute lookup, several times per MIME entity.
A 40 KB header takes about 7 seconds to parse once.
This page as .md · .json · in your agent: get_signal("CVE-2026-116268")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.