CVE-2026-65064: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::HashMap::Shared
Data::HashMap::Shared versions before 0.14 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in shm_generic.h with open(path, O_RDWR | O_CREAT | O_CLOEXEC, 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.
AI Analysis
Technical Summary
The vulnerability in Data::HashMap::Shared (versions <0.14) involves creating a shared memory segment file with overly permissive permissions (mode 0644 after umask) and without safeguards against symlink following or race conditions (missing O_NOFOLLOW and O_EXCL flags). This allows any local user to read the IPC payloads stored in the shared segment and potentially exploit pre-creation or symlink attacks to redirect or manipulate the open() call. The issue stems from the segment creation in shm_generic.h using open(path, O_RDWR | O_CREAT | O_CLOEXEC, 0666).
Potential Impact
Local users on the system can read sensitive inter-process communication data stored in the shared memory segment due to world-readable permissions. Additionally, attackers can exploit race conditions by pre-creating files or symlinks at the target path, potentially redirecting or interfering with the shared memory segment creation. This compromises confidentiality and integrity of IPC data for local users.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to shared directories like /tmp or /dev/shm to trusted users only and monitor for suspicious symlink or file creation. Avoid running vulnerable versions in multi-user environments where local users are untrusted.
CVE-2026-65064: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::HashMap::Shared
Description
Data::HashMap::Shared versions before 0.14 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in shm_generic.h with open(path, O_RDWR | O_CREAT | O_CLOEXEC, 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.
Affected software
pkg:github/Data-HashMap-SharedRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Data::HashMap::Shared (versions <0.14) involves creating a shared memory segment file with overly permissive permissions (mode 0644 after umask) and without safeguards against symlink following or race conditions (missing O_NOFOLLOW and O_EXCL flags). This allows any local user to read the IPC payloads stored in the shared segment and potentially exploit pre-creation or symlink attacks to redirect or manipulate the open() call. The issue stems from the segment creation in shm_generic.h using open(path, O_RDWR | O_CREAT | O_CLOEXEC, 0666).
Potential Impact
Local users on the system can read sensitive inter-process communication data stored in the shared memory segment due to world-readable permissions. Additionally, attackers can exploit race conditions by pre-creating files or symlinks at the target path, potentially redirecting or interfering with the shared memory segment creation. This compromises confidentiality and integrity of IPC data for local users.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict access to shared directories like /tmp or /dev/shm to trusted users only and monitor for suspicious symlink or file creation. Avoid running vulnerable versions in multi-user environments where local users are untrusted.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-07-21T15:29:37.116Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5fcbb72a4a8d5989ac73b4
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/21/2026, 19:52:04 UTC
Last updated: 07/21/2026, 21:09:38 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.