Is CVE-2026-65069 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-65069 being exploited in the wild.

How severe is CVE-2026-65069?

Informational severity, with a CVSS score of 0, published 21 July 2026.

Which products and versions are affected?

EGOR Data DisjointSet::Shared < 0.02.

Is there a fix for CVE-2026-65069?

A patch was published on 2026-07-03: Version 0.02 released with security hardening. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-65069 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-65069?

Check whether you run EGOR Data DisjointSet::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.

CVE-2026-65069: EGOR Data::DisjointSet::Shared insecure file permissions and symlink following

Q: Is there a fix for CVE-2026-65069?

A patch was published on 2026-07-03: Version 0.02 released with security hardening. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-65069 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-65069?

Check whether you run EGOR Data DisjointSet::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.

CVE-2026-65069 · Severity: info · CVSS 0 · Published 2026-07-21

Data::DisjointSet::Shared is a Perl library used for managing shared data structures across different processes. A security flaw in versions before 0.02 allows local users on the same system to read sensitive data stored in these shared memory segments. Additionally, a local attacker could trick the library into using a malicious file, potentially leading to data corruption or unauthorized access to information.

Vendors: EGOR Data.

Quick answers

Is CVE-2026-65069 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-65069 being exploited in the wild.
How severe is CVE-2026-65069?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: EGOR Data DisjointSet::Shared < 0.02.
Is there a fix for CVE-2026-65069?: A patch was published on 2026-07-03: Version 0.02 released with security hardening. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-65069 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-65069?: Check whether you run EGOR Data DisjointSet::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 stems from insecure file operations in dsu.h. Specifically, the library uses open() with mode 0666, which results in world-readable files (0644) under default umask settings. Furthermore, the absence of O_EXCL and O_NOFOLLOW flags allows a local attacker to perform symlink attacks or win a race condition by pre-planting a file in shared directories like /tmp or /dev/shm. This enables unauthorized reading of IPC payloads or redirection of the memory-mapped file to an attacker-controlled location. The issue is resolved in version 0.02, which implements mode 0600 by default.

Affected products

EGOR Data::DisjointSet::Shared < 0.02

Timeline

2026-07-03: patched: Version 0.02 released with security hardening.
2026-07-21: disclosed: CVE-2026-65069 published.

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.