Quick answers
- Is CVE-2026-59147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59147 being exploited in the wild.
- How severe is CVE-2026-59147?
- Informational severity, published 21 July 2026.
- Which products and versions are affected?
- EGOR Data::DisjointSet::Shared before 0.02.
- Is there a fix for CVE-2026-59147?
- 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-59147 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-59147?
- 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 is an out-of-bounds (OOB) read and write (CWE-125, CWE-787) in the dsu_find function of Data::DisjointSet::Shared. While the dsu_validate_header function checks the header and region layout against file size, it fails to validate the actual array contents. An attacker with write access to the backing file can poison the parent array with raw file-stored indices that exceed the node count. When dsu_find performs path compression, it uses these unvalidated indices, leading to OOB memory access. This can result in process crashes or memory corruption. The issue is fixed in version 0.02.
Affected products
- EGOR Data::DisjointSet::Shared before 0.02
Timeline
- 2026-07-03: patched: Version 0.02 released with security hardening.
- 2026-07-21: advisory: CVE-2026-59147 published.