EGOR Data::Buffer::Shared up to 0.04 buf_generic.h open path symlink

Summaryinfo

A vulnerability identified as problematic has been detected in EGOR Data::Buffer::Shared up to 0.04. This issue affects the function Open of the file buf_generic.h of the component Shared. Performing a manipulation of the argument path results in symlink. This vulnerability was named CVE-2026-64613. The attack needs to be approached locally. There is no available exploit.

Detailsinfo

A vulnerability classified as problematic has been found in EGOR Data::Buffer::Shared up to 0.04. This affects the function open of the file buf_generic.h of the component Shared. The manipulation of the argument path with an unknown input leads to a symlink vulnerability. CWE is classifying the issue as CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Data::Buffer::Shared versions before 0.05 for Perl create a world-readable mmap backing file and open it without O_NOFOLLOW. The segment is created in buf_generic.h with open(path, O_RDWR|O_CREAT|O_EXCL, 0666). O_EXCL blocks a pre-seeded file on create, but the mode is 0666, so under the default umask 022 the file is created mode 0644 (world-readable), and O_NOFOLLOW is absent, so a symlink planted at the path is followed when the segment is attached. 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 symlink at the path redirects the open to another file.

The advisory is shared at metacpan.org. This vulnerability is uniquely identified as CVE-2026-64613 since 07/20/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.05 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• EGOR

Name

• Data::Buffer::Shared

Version

• 0.04

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion