# CVE-2026-65063: Data::RadixTree::Shared insecure file permissions and symlink following

Source: https://junglewise.ai/threats/cve-2026-65063-data-radixtree-shared-insecure-file-permissions-and-symlink  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-21. Updated: 2026-07-21  
License: CC BY 4.0 with a link back

CVE-2026-65063 · Severity: info · Published 2026-07-21

Data::RadixTree::Shared, a Perl library used for managing shared memory data structures, contains a security flaw in how it handles temporary files. Because these files are created with insecure permissions and without proper safety checks, a local attacker on the same system could read sensitive data stored in the shared memory or redirect the application to overwrite other files. This could lead to unauthorized data access or system instability.

Vendors: [EGOR Data](https://junglewise.ai/threats/vendors/egor-data).

## Quick answers

**Is CVE-2026-65063 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-65063 being exploited in the wild.

**How severe is CVE-2026-65063?** Informational severity, published 21 July 2026.

**Which products and versions are affected?** EGOR Data RadixTree::Shared before 0.02.

**Is there a fix for CVE-2026-65063?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-65063 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-65063?** Check whether you run EGOR Data RadixTree::Shared at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in radix.h where the mmap backing file is created using open(path, O_RDWR|O_CREAT, 0666). Due to the lack of O_EXCL and O_NOFOLLOW flags, the library is susceptible to symlink attacks and race conditions if the backing file is located in a shared directory like /tmp or /dev/shm. Furthermore, the 0666 mode results in world-readable permissions (typically 0644 under default umasks), allowing any local user to read IPC payloads. An attacker can pre-plant a file or symlink to intercept data or redirect file operations. The issue is addressed in version 0.02.

## Affected products

- EGOR Data::RadixTree::Shared before 0.02

## Timeline

- 2026-07-21: advisory
- 2026-07-21: disclosed

## References

- [https://cpan.org/modules](https://cpan.org/modules)
- [https://metacpan.org/release/EGOR/Data-RadixTree-Shared-0.02/changes](https://metacpan.org/release/EGOR/Data-RadixTree-Shared-0.02/changes)
- [https://metacpan.org/release/EGOR/Data-RadixTree-Shared-0.02/diff/EGOR/Data-RadixTree-Shared-0.01](https://metacpan.org/release/EGOR/Data-RadixTree-Shared-0.02/diff/EGOR/Data-RadixTree-Shared-0.01)