CVE-2026-65068: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::SpatialHash::Shared
Data::SpatialHash::Shared versions before 0.02 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in sphash.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.
AI Analysis
Technical Summary
The vulnerability in Data::SpatialHash::Shared (versions before 0.02) arises from the creation of a backing file with mode 0666 (resulting in 0644 after umask) and opening it without O_EXCL or O_NOFOLLOW flags. This leads to a world-readable mmap file in shared directories like /tmp or /dev/shm, exposing IPC payloads to local users. The absence of O_NOFOLLOW allows symlink following, and the lack of O_EXCL permits silent use of pre-existing files, enabling local attackers to perform pre-creation race or redirection attacks.
Potential Impact
Local users can read sensitive IPC data stored in the world-readable shared memory segment. They can also exploit race conditions or symlink redirection to manipulate the file open operation, potentially leading to unauthorized data access or interference with IPC mechanisms.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running the vulnerable versions in environments where local users are untrusted or can access shared directories. Consider restricting permissions on the shared directory or using alternative IPC mechanisms with secure file handling.
CVE-2026-65068: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::SpatialHash::Shared
Description
Data::SpatialHash::Shared versions before 0.02 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in sphash.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.
Affected software
pkg:github/Data-SpatialHash-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::SpatialHash::Shared (versions before 0.02) arises from the creation of a backing file with mode 0666 (resulting in 0644 after umask) and opening it without O_EXCL or O_NOFOLLOW flags. This leads to a world-readable mmap file in shared directories like /tmp or /dev/shm, exposing IPC payloads to local users. The absence of O_NOFOLLOW allows symlink following, and the lack of O_EXCL permits silent use of pre-existing files, enabling local attackers to perform pre-creation race or redirection attacks.
Potential Impact
Local users can read sensitive IPC data stored in the world-readable shared memory segment. They can also exploit race conditions or symlink redirection to manipulate the file open operation, potentially leading to unauthorized data access or interference with IPC mechanisms.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running the vulnerable versions in environments where local users are untrusted or can access shared directories. Consider restricting permissions on the shared directory or using alternative IPC mechanisms with secure file handling.
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: 6a5fcbb92a4a8d5989ac73d1
Added to database: 07/21/2026, 19:42:49 UTC
Last enriched: 07/21/2026, 19:51:36 UTC
Last updated: 07/21/2026, 21:09:40 UTC
Views: 6
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.