CVE-2026-65065: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::RoaringBitmap::Shared
Data::RoaringBitmap::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 roaring.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::RoaringBitmap::Shared (CVE-2026-65065) arises from the creation of a shared memory segment file with mode 0666 (resulting in 0644 after umask), making it world-readable. The file is opened without O_EXCL or O_NOFOLLOW flags, allowing an attacker to plant a symlink or pre-existing file at the target path. This enables local attackers to read inter-process communication payloads and potentially exploit race conditions or redirect file operations. The issue is due to incorrect permission assignment (CWE-732) and unsafe file handling (CWE-59).
Potential Impact
Local attackers can read sensitive IPC data stored in the shared memory segment due to world-readable file permissions. They can also exploit race conditions by pre-creating files or symlinks at the target path, potentially redirecting file operations. The vulnerability compromises confidentiality but does not affect integrity or availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local user access to shared directories like /tmp or /dev/shm where the segment files are created. Avoid running vulnerable versions in multi-user environments where untrusted local users exist.
CVE-2026-65065: CWE-732 Incorrect Permission Assignment for Critical Resource in EGOR Data::RoaringBitmap::Shared
Description
Data::RoaringBitmap::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 roaring.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.
CVSS v3.1
Score 5.5medium
Affected software
pkg:github/Data-RoaringBitmap-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::RoaringBitmap::Shared (CVE-2026-65065) arises from the creation of a shared memory segment file with mode 0666 (resulting in 0644 after umask), making it world-readable. The file is opened without O_EXCL or O_NOFOLLOW flags, allowing an attacker to plant a symlink or pre-existing file at the target path. This enables local attackers to read inter-process communication payloads and potentially exploit race conditions or redirect file operations. The issue is due to incorrect permission assignment (CWE-732) and unsafe file handling (CWE-59).
Potential Impact
Local attackers can read sensitive IPC data stored in the shared memory segment due to world-readable file permissions. They can also exploit race conditions by pre-creating files or symlinks at the target path, potentially redirecting file operations. The vulnerability compromises confidentiality but does not affect integrity or availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local user access to shared directories like /tmp or /dev/shm where the segment files are created. Avoid running vulnerable versions in multi-user environments where untrusted local users exist.
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: 6a5fcbb72a4a8d5989ac73b8
Added to database: 07/21/2026, 19:42:47 UTC
Last enriched: 07/30/2026, 01:31:57 UTC
Last updated: 09/03/2026, 10:52:10 UTC
Views: 63
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.