EGOR Data::RingBuffer::Shared up to 0.3 ring.h open path toctou

Summaryinfo

A vulnerability was found in EGOR Data::RingBuffer::Shared up to 0.3. It has been rated as problematic. Impacted is the function Open of the file ring.h. Performing a manipulation of the argument path results in toctou. This vulnerability is known as CVE-2026-65066. Attacking locally is a requirement. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in EGOR Data::RingBuffer::Shared up to 0.3. This affects the function open of the file ring.h. The manipulation of the argument path with an unknown input leads to a toctou vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Data::RingBuffer::Shared versions before 0.04 for Perl create a world-readable mmap backing file and open it without O_EXCL or O_NOFOLLOW. The segment is created in ring.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 at metacpan.org. This vulnerability is uniquely identified as CVE-2026-65066 since 07/21/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading to version 0.04 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Programming Language Software

Vendor

• EGOR

Name

• Data::RingBuffer::Shared

Version

• 0.1
• 0.2
• 0.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion