CVE-2026-65067: Data::Intern::Shared versions before 0.02 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW
Data::Intern::Shared versions before 0.02 for Perl create a world-readable mmap backing file and open it without OEXCL or ONOFOLLOW.
The segment is created in intern.h with open(path, ORDWR|OCREAT, 0666). The mode is 0666, so under the default umask 022 the file is created mode 0644 (world-readable). ONOFOLLOW is absent, so a symlink planted at the path is followed, and OEXCL is absent, so the open silently uses a pre-planted file instead of failing.
A "Shared" segment naturally lives in a shared directory such as /tmp or /dev/shm, where any local user can read the IPC payloads stored in the world-readable segment, and a pre-planted file or symlink at the path lets a local attacker win a pre-creation race or redirect the open.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Data::Intern::Sharedto a version that resolves this vulnerability.Fixed in 0.02
Event History
Frequently Asked Questions
What is the severity of CVE-2026-65067?
CVE-2026-65067 has a low severity score of 3.8 according to the CVSS v3.1.
How does CVE-2026-65067 affect Data::Intern::Shared for Perl?
CVE-2026-65067 affects Data::Intern::Shared by creating a world-readable mmap backing file due to improper file permissions.
Is there a fix for CVE-2026-65067?
To fix CVE-2026-65067, upgrade Data::Intern::Shared to version 0.02 or later.
What are the risks associated with CVE-2026-65067?
The primary risk of CVE-2026-65067 is unauthorized access to sensitive data due to world-readable file permissions.
What versions of Data::Intern::Shared are vulnerable to CVE-2026-65067?
Versions of Data::Intern::Shared prior to 0.02 are vulnerable to CVE-2026-65067.