Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local shell access
-
ExploitPlace symlink or pre-create file in target shared directory
-
ExecutionTrigger application to open mmap file
-
ImpactRead world-readable file to capture IPC payloads
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Permission assignment review
|
| Exploitation Conditions | Exploitation requires local low-privileged access to the system and the ability to place files or symlinks in the directory where the shared segment is created, which by default is a world-writable location like /tmp or /dev/shm. The vulnerability is exploitable as long as the application uses a Shared segment with the default configuration. No authentication beyond being a local user is needed, and no user interaction is required. The attack is limited to information disclosure; it does not allow code execution or system compromise beyond reading the segment contents. |
| Impact | The CVSS vector indicates a local attack vector, low complexity, and low privileges required, yielding a medium base score of 5.5. However, EPSS probability is only 0.16% (6th percentile), and the vulnerability is not listed in CISA KEV. No public proof-of-concept exploit or active exploitation has been identified. Using SSVC, exploitation is 'none', automatable is 'yes' given the ease of symlink planting, and technical impact is 'partial' (confidentiality only). The real-world risk is low due to the niche nature of the Perl module and lack of attacker activity, despite the CVSS score. CVSS suggests local access, which is accurate; no conflicting signals. |
| Exploit ScenarioDerived | A local attacker with a shell account on the host creates a symlink in /dev/shm pointing to a file they can later read, or pre-creates a world-readable file at the expected path of the shared segment. When the vulnerable application starts and opens the mmap file, the attacker reads the exposed IPC data, potentially obtaining sensitive information passed between processes. The attack can be executed without user interaction and only requires the ability to write to the shared directory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 26, 2026
Information disclosure in Data::RoaringBitmap::Shared Perl module before 0.02 allows local attackers to read sensitive IPC payloads from world-readable mmap backing files. The module creates files with insecure permissions in shared directories, while missing O_NOFOLLOW and O_EXCL flags enable symlink and race attacks. No active exploitation or public exploit code is known, and the EPSS score is low.
RemediationAI
Upgrade to Data::RoaringBitmap::Shared version 0.02, which resolves the issue. The vendor-released patch modifies the file creation flags and permissions in roaring.h (see the diff at https://metacpan.org/release/EGOR/Data-RoaringBitmap-Shared-0.02/diff/EGOR/Data-RoaringBitmap-Shared-0.01#roaring.h). If immediate patching is not possible, ensure the directory used for shared segments is not world-writable (e.g., avoid /tmp or /dev/shm) and restrict access to the application's private directory with appropriate permissions; note this may change application design and could break functionality relying on default shared locations.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Data::RoaringBitmap::Shared is a Perl module that provides shared-memory segments for roaring bitmaps, commonly stored in world-writable directories like /tmp or /dev/shm. The vulnerability stems from CWE-732: the roaring.h source opens the backing file using open(path, O_RDWR|O_CREAT, 0666), which under default umask creates a world-readable file (mode 0644). Additionally, the open call lacks O_NOFOLLOW, so symlinks are followed, and lacks O_EXCL, allowing a pre-existing file to be silently reused instead of failing. This design flaw exposes the shared IPC data to any local user who can place a symlink or file before the segment is created.
Know when Data gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Local attack vector, low complexity, low privileges; only confidentiality impact (information disclosure).
Primary rating from Vendor (CPANSec).
CVSS VectorVendor: CPANSec
Lifecycle Timeline
3DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
The Data::Validate::IP module through 0.29 for Perl does not properly consider extraneous zero characters at the beginni
Stack buffer overflow in the Perl module Data::RingBuffer::Shared before 0.04 lets a local peer with write access to the
Out-of-bounds read and write in the Perl module Data::DisjointSet::Shared before version 0.02 lets a local actor who can
Out-of-bounds memory disclosure in Data::Intern::Shared before 0.02, a Perl shared-memory string interning module, lets
Out-of-bounds read and write in the Perl module Data::SpatialHash::Shared before 0.02 lets a local peer with write acces
Entropy source compromise in Data::Entropy (Perl) before version 0.010 allows any on-path network attacker to fully cont
Out-of-bounds read in Data::RoaringBitmap::Shared before version 0.02 for Perl allows a local peer with write access to
World-readable mmap backing files and absent O_NOFOLLOW protection in Data::Buffer::Shared for Perl (versions before 0.0
Insecure mmap backing-file creation in Data::DisjointSet::Shared (Perl/CPAN) before 0.02 exposes inter-process IPC paylo
Information disclosure in the Perl Data::Deque::Shared module before version 0.06 exposes inter-process communication qu
World-readable IPC segment exposure in Data::SpatialHash::Shared (Perl) before version 0.02 allows any local user on a m
Insecure file creation in Data::Intern::Shared for Perl (all versions before 0.02) exposes shared memory IPC payloads to
EUVD-2026-46378
GHSA-g774-r9mw-4c65
NVD
CVE.org
EPSS
VulDB
Exploit-DB