Is CVE-2026-59140 exploited in the wild?

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

How severe is CVE-2026-59140?

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

Which products and versions are affected?

Vividsnow Data::SortedSet::Shared < 0.03.

Is there a fix for CVE-2026-59140?

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-59140 attacked?

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

Am I affected by CVE-2026-59140?

Check whether you run Vividsnow Data::SortedSet::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-59140: Perl Data::SortedSet::Shared out-of-bounds read in query paths

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

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.

Q: How is CVE-2026-59140 attacked?

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

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

Check whether you run Vividsnow Data::SortedSet::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-59140 · Severity: info · CVSS 0 · Published 2026-07-21

Data::SortedSet::Shared is a Perl library used to manage sorted data sets in shared memory. A vulnerability in how the library handles shared data files allows a local user with write access to those files to corrupt the internal data structure. This can cause applications using the library to crash or potentially leak sensitive information from the computer's memory.

Vendors: Vividsnow.

Quick answers

Is CVE-2026-59140 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59140 being exploited in the wild.
How severe is CVE-2026-59140?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: Vividsnow Data::SortedSet::Shared < 0.03.
Is there a fix for CVE-2026-59140?: 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-59140 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-59140?: Check whether you run Vividsnow Data::SortedSet::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

An out-of-bounds (OOB) read vulnerability exists in Data::SortedSet::Shared due to insufficient validation of node indices within mmap'd segments. While the attach-time validator 'ss_validate_header' checks the root index, it fails to bound child, leftmost, or rightmost node indices against the 'node_capacity'. A local attacker with write access to the backing file can poison these tree links. Subsequent rank, min, or max queries will then dereference these unvalidated indices, leading to an OOB read that can result in a process crash or disclosure of adjacent memory. The issue is addressed in version 0.03.

Affected products

EGOR (vividsnow) Data::SortedSet::Shared < 0.03

Timeline

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

References

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