CVE-2026-59140
Local OOB read in Perl Data::SortedSet::Shared via poisoned mmap tree indices
Is CVE-2026-59140 being exploited?
Not confirmed. CVE-2026-59140 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.54% probability of exploitation in the next 30 days.
How severe is CVE-2026-59140?
CVE-2026-59140 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-59140?
Yes. A fix has been recorded for CVE-2026-59140. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59140 affect?
CVE-2026-59140 affects Perl Data::SortedSet::Shared < 0.03, Perl applications using Data::SortedSet::Shared, Systems allowing untrusted writes to module backing files. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59140?
Upgrade to Data::SortedSet::Shared 0.03; restrict backing-file write access and validate files
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local actor with write access to the backing file can trigger out-of-bounds reads, causing info disclosure or process crash.
Patch when possible
- affected< 0.03
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.