Skip to content
Applications

CVE-2026-59145

9.1
Critical
EPSS 0.54%Patch availableJul 23, 2026

Out-of-bounds read in Perl Data::Intern::Shared allowing local file-based memory disclosure

common questions

Is CVE-2026-59145 being exploited?

Not confirmed. CVE-2026-59145 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-59145?

CVE-2026-59145 is rated Critical with a CVSS score of 9.1. 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-59145?

Yes. A fix has been recorded for CVE-2026-59145. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59145 affect?

CVE-2026-59145 affects Perl Data::Intern::Shared < 0.02, Perl apps using Data::Intern::Shared, Systems using file-backed interning tables. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59145?

Upgrade Data::Intern::Shared to >= 0.02 and restrict write access to backing files.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Perl Data::Intern::Shared < 0.02Perl apps using Data::Intern::SharedSystems using file-backed interning tables
impact

Local attacker who can modify the module's backing file can trigger OOB reads to disclose adjacent process memory and file-controlled data.

action required

Immediate action required

affected versions
EGOR Data::Intern::Shared
  • affected< 0.02

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free