UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-116265

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.

Properties

Last source
NVD
Nvd fetched at
2026-10-28T19:43:42.952230+00:00
Cve id
CVE-2026-116265
First seen by Signal
2026-10-28T19:44:28+00:00
Retrieved at
2026-10-28T19:44:28+00:00
Published at
2026-10-28T18:17:12.910
Last modified
2026-10-28T18:17:12.910

Related Entities (1)

HAS_WEAKNESS (1)

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-116265 — Ninja Signal Threat Intelligence | Ninja Signal