The vulnerability in Data::DisjointSet::Shared (versions before 0.02) arises from incorrect permission assignment and unsafe file opening practices for its mmap backing file. The file is created with mode 0666, which under default umask results in a world-readable file (0644). The open call does not use O_EXCL, allowing silent use of pre-existing files, and lacks O_NOFOLLOW, enabling symlink following. Since the shared segment resides in directories accessible by local users (e.g., /tmp, /dev/shm), this permits local attackers to read IPC payloads or exploit race conditions by pre-creating files or symlinks at the target path.

Local attackers can read sensitive IPC payloads stored in the world-readable mmap backing file. They can also exploit race conditions or symlink following to redirect file operations, potentially leading to unauthorized information disclosure or manipulation of IPC resources.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict local user access to shared directories where the mmap backing file is created, and avoid running vulnerable versions in multi-user environments. Monitor vendor channels for updates addressing the use of safer open flags (O_EXCL, O_NOFOLLOW) and stricter file permissions.