CVE-2026-64617: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::PubSub::Shared
Data::PubSub::Shared versions before 0.07 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in pubsub.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::PubSub::Shared (CVE-2026-64617) arises from incorrect permission assignment and unsafe file opening practices in versions prior to 0.07. Specifically, the mmap backing file is created with mode 0666 (resulting in world-readable files under typical umask settings) and opened without O_EXCL or O_NOFOLLOW flags. This allows local attackers to read sensitive IPC data and exploit race conditions or symlink redirection attacks by pre-creating files or symlinks in shared directories. The issue is categorized under CWE-732 (Incorrect Permission Assignment for Critical Resource) and CWE-59 (Improper Link Resolution).
Potential Impact
Local users on the system can read inter-process communication payloads stored in the world-readable shared memory segment, potentially exposing sensitive data. Additionally, attackers can exploit race conditions or symlink redirection to manipulate the file open operation, possibly leading to unauthorized file access or modification. There is no indication of remote exploitation or known exploits in the wild.
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 vulnerable versions (<0.07) in environments where untrusted local users have access to shared directories such as /tmp or /dev/shm. Consider restricting permissions on the shared directory or using alternative IPC mechanisms that enforce stricter access controls.
CVE-2026-64617: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::PubSub::Shared
Description
Data::PubSub::Shared versions before 0.07 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in pubsub.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-PubSub-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::PubSub::Shared (CVE-2026-64617) arises from incorrect permission assignment and unsafe file opening practices in versions prior to 0.07. Specifically, the mmap backing file is created with mode 0666 (resulting in world-readable files under typical umask settings) and opened without O_EXCL or O_NOFOLLOW flags. This allows local attackers to read sensitive IPC data and exploit race conditions or symlink redirection attacks by pre-creating files or symlinks in shared directories. The issue is categorized under CWE-732 (Incorrect Permission Assignment for Critical Resource) and CWE-59 (Improper Link Resolution).
Potential Impact
Local users on the system can read inter-process communication payloads stored in the world-readable shared memory segment, potentially exposing sensitive data. Additionally, attackers can exploit race conditions or symlink redirection to manipulate the file open operation, possibly leading to unauthorized file access or modification. There is no indication of remote exploitation or known exploits in the wild.
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 vulnerable versions (<0.07) in environments where untrusted local users have access to shared directories such as /tmp or /dev/shm. Consider restricting permissions on the shared directory or using alternative IPC mechanisms that enforce stricter access controls.
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: 6a5fcbb72a4a8d5989ac73a4
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/21/2026, 19:52:36 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.