CVE-2026-116265

libmime-tools-perl: MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231...

CVE-2026-116265 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-116265, released November 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.3
medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0021
10th percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
libmime-tools-perl · Debian 14 5.522-1 DEBIAN-CVE-2026-116265 Nov 3, 2026
perl-MIME-tools · Fedora 43 5.522-1.fc43 FEDORA-2026-A415B3BF48 Nov 7, 2026
perl-MIME-tools · opensuse-leap 16.0 5.522.0-bp160.1.1 OPENSUSE-SU-2026:22226-1 Nov 7, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.