CVE-2026-116265: MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary
Source GCVE Database
Not known to be exploited : upgrade to 5.521 soon.
Data as of 28 Oct 2026, 19:42 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 5.521
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade MIME-tools (Perl module) to 5.521.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MIME-tools | Affected
| Fixed in
|
CPANMIME-toolspkg:cpan/MIME-toolsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should be aware of this limitation in MIME::Field::ParamVal and consider additional filtering or inspection methods outside of ambiguous_content() reliance.
Description
MIME::Field::ParamVal versions before 5.521 for Perl do not properly flag ambiguous multipart boundaries when written as RFC 2231 continuations. This flaw allows a remote sender to craft a MIME message that causes MIME::Parser to split the message on a different boundary than other mail readers, potentially hiding attachments from filters relying on ambiguous_content() checks while the recipient's mail client displays them.