EGOR Data::SpatialHash::Shared up to 0.1 Symlink Following sphash.h open symlink

Summaryinfo

A vulnerability described as problematic has been identified in EGOR Data::SpatialHash::Shared up to 0.1. This affects the function Open of the file sphash.h of the component Symlink Following. Executing a manipulation can lead to symlink. The identification of this vulnerability is CVE-2026-65068. The attack can only be executed locally. There is no exploit available.

Detailsinfo

A vulnerability has been found in EGOR Data::SpatialHash::Shared up to 0.1 and classified as problematic. This vulnerability affects the function open of the file sphash.h of the component Symlink Following. The manipulation with an unknown input leads to a symlink vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Data::SpatialHash::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 sphash.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 was named CVE-2026-65068 since 07/21/2026. The exploitation appears 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.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• EGOR

Name

• Data::SpatialHash::Shared

Version

• 0.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion