Live › vulnerability › CVE-2026-116271
Go to dashboardMIME::Parser::FileUnder before 5.521 reuses an existing output directory and opens files by following symlinks inside it. A local user who can write to a shared output base such as /tmp can make the parser write attachments to a file of their choosing, with the parsing process's privileges.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 18:34 UTC. All times on this page are UTC.
Teams that run Perl code using MIME::Parser::FileUnder with output_under pointing at a directory other local users can write to, such as /tmp. Parsing mail in a directory only the service user can write to removes the local symlink path. unknown whether the sources list any other exposure.
No product ranges from the sources yet.
perl -MMIME::Parser -e 'print $MIME::Parser::VERSION' and check whether it is below 5.521output_under on a shared, world-writable directory such as /tmp5.521 or later/tmpEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
MIME::Parser::FileUnder versions before 5.521 for Perl reuse a pre-created output directory and follow symlinks in it, letting local users redirect attachment writes.
Each message is written to a directory named msg-<time>-<pid>-<n> under the output base, and an existing directory of that name is used as is. A file name counts as unused when nothing exists at that path, which holds for a dangling symlink, and the body file is then opened in a way that follows the link.
When the output base is writable by other users, as with output_under("/tmp"), a local user can pre-create the directory with a symlink named like an attachment. The parser then writes the attachment to the link target with the privileges of the parsing process.
This page as .md · .json · in your agent: get_signal("CVE-2026-116271")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.