CVE-2026-64616: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::NDArray::Shared
Data::NDArray::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 ndarray.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::NDArray::Shared (versions <0.02) arises from the creation of a mmap 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 file in shared directories, enabling local users to read sensitive IPC data. The absence of O_NOFOLLOW allows symlink following, and the absence of O_EXCL allows silent opening of pre-existing files, facilitating pre-creation race or symlink redirection attacks. This is classified under CWE-732 (Incorrect Permission Assignment) and CWE-59 (Link Following).
Potential Impact
Local users on the system can read sensitive inter-process communication data stored in the mmap segment due to world-readable permissions. Additionally, attackers can exploit race conditions or symlink redirection to manipulate the file opened by the application, 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 Data::NDArray::Shared in environments where untrusted local users have access to shared directories like /tmp or /dev/shm. Consider restricting permissions on these directories or using alternative IPC mechanisms that do not expose sensitive data via world-readable files.
CVE-2026-64616: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::NDArray::Shared
Description
Data::NDArray::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 ndarray.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-NDArray-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::NDArray::Shared (versions <0.02) arises from the creation of a mmap 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 file in shared directories, enabling local users to read sensitive IPC data. The absence of O_NOFOLLOW allows symlink following, and the absence of O_EXCL allows silent opening of pre-existing files, facilitating pre-creation race or symlink redirection attacks. This is classified under CWE-732 (Incorrect Permission Assignment) and CWE-59 (Link Following).
Potential Impact
Local users on the system can read sensitive inter-process communication data stored in the mmap segment due to world-readable permissions. Additionally, attackers can exploit race conditions or symlink redirection to manipulate the file opened by the application, 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 Data::NDArray::Shared in environments where untrusted local users have access to shared directories like /tmp or /dev/shm. Consider restricting permissions on these directories or using alternative IPC mechanisms that do not expose sensitive data via world-readable files.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-07-20T11:30:10.287Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5fcbb72a4a8d5989ac73a0
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/21/2026, 19:52:44 UTC
Last updated: 07/21/2026, 21:09:31 UTC
Views: 4
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.