The vulnerability in Data::SpatialHash::Shared (versions <0.02) arises from creating a shared memory segment file with mode 0666 (resulting in 0644 after umask) and opening it without O_EXCL or O_NOFOLLOW flags. This leads to a world-readable backing file in shared directories like /tmp or /dev/shm, exposing IPC data to local users. The absence of O_NOFOLLOW allows symlink following, enabling local attackers to redirect the open call to attacker-controlled files. The lack of O_EXCL permits silent use of pre-existing files, facilitating pre-creation race attacks.

Local attackers can read sensitive IPC payloads stored in the world-readable shared memory segment. They may also exploit race conditions or symlink redirection to manipulate the file open operation, potentially leading to unauthorized information disclosure or interference with IPC mechanisms. The CVSS score of 3.8 indicates a low severity impact limited to local privilege and confidentiality loss without integrity or availability impact.

No official patch or remediation level is currently documented. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider restricting permissions on the shared directory, avoid running vulnerable versions in multi-user environments, or apply manual mitigations such as ensuring the backing file is created with stricter permissions and using secure open flags if possible.