Data::SortedSet::Shared versions before 0.03 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW

MITRE NVD CVE.ORG JSON API Print: PDF PDF

Summary

CVECVE-2026-65062
StatePUBLISHED
AssignerCPANSec
Source PriorityCVE Program / NVD first with legacy fallback
Published2026-07-21 20:17:05 UTC
Updated2026-07-21 20:17:05 UTC
DescriptionData::SortedSet::Shared versions before 0.03 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in sortedset.h with open(path, O_RDWR|O_CREAT, 0666). The mode is 0666, so under the default umask 022 the file is created mode 0644 (world-readable). O_NOFOLLOW is absent, so a symlink planted at the path is followed, and O_EXCL 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.

Risk And Classification

Problem Types: CWE-59 | CWE-732 | CWE-732 CWE-732 Incorrect Permission Assignment for Critical Resource | CWE-59 CWE-59 Improper Link Resolution Before File Access

Vendor Declared Affected Products

SourceVendorProductVersionPlatforms
CNA EGOR DataSortedSetShared affected 0.03 custom Not specified

References

ReferenceSourceLinkTags
metacpan.org/release/EGOR/Data-SortedSet-Shared-0.03/changes 9b29abf9-4ab0-4765-b253-1875cd9b441e metacpan.org
metacpan.org/release/EGOR/Data-SortedSet-Shared-0.03/diff/EGOR/Data-Sorted... 9b29abf9-4ab0-4765-b253-1875cd9b441e metacpan.org
CVE Program record CVE.ORG www.cve.org canonical
NVD vulnerability detail NVD nvd.nist.gov canonical, analysis

Additional Advisory Data

Solutions

CNA: Upgrade to Data::SortedSet::Shared 0.03 or later, which creates the backing file mode 0600 (owner-only) with O_EXCL and O_NOFOLLOW.

Workarounds

CNA: For deployments that cannot upgrade to 0.03, set a restrictive umask so the backing file is not world-readable and place it in a directory only the owning user can access.

© CVE.report 2026

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

Free CVE JSON API cve.report/api

CVE.report and Source URL Uptime Status status.cve.report