{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-116266 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-116266 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-116266 is a vulnerability, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-116266 and fix it if it is affected.\n\nWhat it is: CVE-2026-116266 is a vulnerability, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-116266 in the wild and no public exploit code.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-116266/ (Markdown: https://insights.sbomify.com/CVE-2026-116266/index.md)","id":"CVE-2026-116266","markdown":"https://insights.sbomify.com/CVE-2026-116266/index.md","name":"CVE-2026-116266","record":{"aliases":["DEBIAN-CVE-2026-116266","GHSA-c5m8-q98x-42wx","UBUNTU-CVE-2026-116266"],"analysis":null,"analysis_generated_by":null,"assigner":"CPANSec","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous.\n\nThe multipart_boundary() method decodes RFC 2047 encoded words anywhere in the boundary, but the ambiguity check only fires when the whole value is one encoded word. A boundary such as abc=?us-ascii?Q?def?= is used as abcdef, and ambiguous_content() returns false.\n\nEncoded words are not allowed in parameters, so other mail readers split the message on the literal value. A remote sender can hide an attachment from a filter that relies on ambiguous_content() while the recipient's mail client shows it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MIME::Head versions from 5.518 before 5.521 for Perl decode a partly encoded multipart boundary without flagging the parse as ambiguous.","id":"CVE-2026-116266","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MIME::Parser versions before 5.521 for Perl allow memory exhaustion via indented error messages from a truncated, deeply nested message.","id":"CVE-2026-116267"},"packages":[],"prev":{"headline":"MIME::Field::ParamVal versions before 5.521 for Perl do not flag an ambiguous multipart boundary written as RFC 2231 continuations.","id":"CVE-2026-116265"},"products":[],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-116266/"}