{"api_version":"1","generated_at":"2026-10-29T06:14:48+00:00","cve":"CVE-2026-116265","urls":{"html":"https://cve.report/CVE-2026-116265","api":"https://cve.report/api/cve/CVE-2026-116265.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-116265","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-116265"},"summary":{"title":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations","description":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations.\n\nThe 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.\n\nA 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.","state":"PUBLISHED","assigner":"CPANSec","published_at":"2026-10-28 18:17:12","updated_at":"2026-10-28 18:17:12"},"problem_types":["CWE-436","CWE-436 CWE-436 Interpretation Conflict"],"metrics":[],"references":[{"url":"https://metacpan.org/release/DSKOLL/MIME-tools-5.521/changes","name":"https://metacpan.org/release/DSKOLL/MIME-tools-5.521/changes","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-116265","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-116265","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to MIME-tools 5.521 or later.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"collectionURL":"https://cpan.org/modules","defaultStatus":"unaffected","modules":["MIME::Field::ParamVal"],"packageName":"MIME-tools","packageURL":"pkg:cpan/MIME-tools","programFiles":["lib/MIME/Field/ParamVal.pm"],"programRoutines":[{"name":"MIME::Field::ParamVal::parse_params"}],"repo":"https://salsa.debian.org/dskoll/mime-tools","versions":[{"lessThan":"5.521","status":"affected","version":"0","versionType":"custom"}]}],"descriptions":[{"lang":"en","value":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations.\n\nThe 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.\n\nA 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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-436","description":"CWE-436 Interpretation Conflict","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-28T17:32:11.827Z","orgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","shortName":"CPANSec"},"references":[{"tags":["release-notes"],"url":"https://metacpan.org/release/DSKOLL/MIME-tools-5.521/changes"}],"solutions":[{"lang":"en","value":"Upgrade to MIME-tools 5.521 or later."}],"source":{"discovery":"UNKNOWN"},"title":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations","x_generator":{"engine":"cpansec-cna-tool 0.1"}}},"cveMetadata":{"assignerOrgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","assignerShortName":"CPANSec","cveId":"CVE-2026-116265","datePublished":"2026-10-28T17:32:11.827Z","dateReserved":"2026-10-25T18:05:02.235Z","dateUpdated":"2026-10-28T17:32:11.827Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-28 18:17:12","lastModifiedDate":"2026-10-28 18:17:12","problem_types":["CWE-436","CWE-436 CWE-436 Interpretation Conflict"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"116265","Ordinal":"1","Title":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag","CVE":"CVE-2026-116265","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"116265","Ordinal":"1","NoteData":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations.\n\nThe 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.\n\nA 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.","Type":"Description","Title":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag"}]}}}