CVE-2026-65063: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::RadixTree::Shared
Data::RadixTree::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 radix.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::RadixTree::Shared (versions before 0.02) arises from incorrect permission assignment (CWE-732) and unsafe file opening practices (CWE-59). Specifically, the mmap backing file is created with mode 0666, which under default umask results in a world-readable file. The open call lacks O_NOFOLLOW and O_EXCL flags, allowing an attacker to exploit symlink redirection and pre-creation race conditions. Since the shared segment typically resides in shared directories accessible by local users, this can lead to unauthorized local users reading IPC payloads or manipulating the file path to influence the open operation.
Potential Impact
Local users can read sensitive IPC payloads stored in the world-readable mmap backing file. Additionally, attackers can exploit symlink redirection and pre-creation race conditions to manipulate the file open operation, potentially leading to unauthorized access or interference with the shared memory segment. This compromises confidentiality and integrity of IPC data on the affected system.
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 in environments where local users are untrusted or can access shared directories such as /tmp or /dev/shm. Restricting permissions on the shared directory or using alternative IPC mechanisms with secure file handling may reduce risk.
CVE-2026-65063: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::RadixTree::Shared
Description
Data::RadixTree::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 radix.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-RadixTree-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::RadixTree::Shared (versions before 0.02) arises from incorrect permission assignment (CWE-732) and unsafe file opening practices (CWE-59). Specifically, the mmap backing file is created with mode 0666, which under default umask results in a world-readable file. The open call lacks O_NOFOLLOW and O_EXCL flags, allowing an attacker to exploit symlink redirection and pre-creation race conditions. Since the shared segment typically resides in shared directories accessible by local users, this can lead to unauthorized local users reading IPC payloads or manipulating the file path to influence the open operation.
Potential Impact
Local users can read sensitive IPC payloads stored in the world-readable mmap backing file. Additionally, attackers can exploit symlink redirection and pre-creation race conditions to manipulate the file open operation, potentially leading to unauthorized access or interference with the shared memory segment. This compromises confidentiality and integrity of IPC data on the affected system.
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 in environments where local users are untrusted or can access shared directories such as /tmp or /dev/shm. Restricting permissions on the shared directory or using alternative IPC mechanisms with secure file handling may reduce risk.
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: 6a5fcbb72a4a8d5989ac73b0
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/21/2026, 19:52:12 UTC
Last updated: 07/21/2026, 21:09:33 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.