CVE-2026-64614: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::Deque::Shared
Data::Deque::Shared versions before 0.06 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in deque.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::Deque::Shared (versions <0.06) arises from incorrect permission assignment and insecure file opening practices. The mmap backing file is created with mode 0666, which under default umask 022 results in a world-readable file (0644). The open call does not use O_EXCL, allowing an attacker to pre-place a file at the target path without causing open to fail, and lacks O_NOFOLLOW, enabling symlink following. Since the shared segment resides in directories accessible by local users (e.g., /tmp or /dev/shm), this permits local attackers to read IPC payloads or manipulate the file open operation to their advantage.
Potential Impact
Local attackers can read sensitive inter-process communication (IPC) data stored in the world-readable shared memory segment. They can also exploit the absence of O_EXCL and O_NOFOLLOW to perform pre-creation race attacks or redirect file opens via symlinks, potentially leading to unauthorized data disclosure or interference with the shared resource.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid running Data::Deque::Shared versions prior to 0.06 in multi-user environments or restrict access to the shared directories to trusted users only. Monitoring for updates from the EGOR project is recommended to apply any official fixes once released.
CVE-2026-64614: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::Deque::Shared
Description
Data::Deque::Shared versions before 0.06 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in deque.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
Run 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::Deque::Shared (versions <0.06) arises from incorrect permission assignment and insecure file opening practices. The mmap backing file is created with mode 0666, which under default umask 022 results in a world-readable file (0644). The open call does not use O_EXCL, allowing an attacker to pre-place a file at the target path without causing open to fail, and lacks O_NOFOLLOW, enabling symlink following. Since the shared segment resides in directories accessible by local users (e.g., /tmp or /dev/shm), this permits local attackers to read IPC payloads or manipulate the file open operation to their advantage.
Potential Impact
Local attackers can read sensitive inter-process communication (IPC) data stored in the world-readable shared memory segment. They can also exploit the absence of O_EXCL and O_NOFOLLOW to perform pre-creation race attacks or redirect file opens via symlinks, potentially leading to unauthorized data disclosure or interference with the shared resource.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should avoid running Data::Deque::Shared versions prior to 0.06 in multi-user environments or restrict access to the shared directories to trusted users only. Monitoring for updates from the EGOR project is recommended to apply any official fixes once released.
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: 6a5fcbb72a4a8d5989ac7398
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/21/2026, 19:53:01 UTC
Last updated: 07/21/2026, 21:09:25 UTC
Views: 3
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.