EGOR Data::RoaringBitmap::Shared up to 0.01 roaring.h path toctou

Summaryinfo

A vulnerability was found in EGOR Data::RoaringBitmap::Shared up to 0.01. It has been declared as problematic. This issue affects some unknown processing of the file roaring.h. Such manipulation of the argument path leads to toctou. This vulnerability is traded as CVE-2026-65065. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in EGOR Data::RoaringBitmap::Shared up to 0.01. Affected by this issue is some unknown processing of the file roaring.h. The manipulation of the argument path with an unknown input leads to a toctou vulnerability. Using CWE to declare the problem leads to CWE-367. The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at metacpan.org. This vulnerability is handled as CVE-2026-65065 since 07/21/2026. The exploitation is known to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.

Upgrading to version 0.02 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Programming Language Software

Vendor

• EGOR

Name

• Data::RoaringBitmap::Shared

Version

• 0.01

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion