Is CVE-2026-59141 exploited in the wild?

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

How severe is CVE-2026-59141?

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

Which products and versions are affected?

EGOR Data::RadixTree::Shared < 0.02.

Is there a fix for CVE-2026-59141?

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

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

Am I affected by CVE-2026-59141?

Check whether you run EGOR Data::RadixTree::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-59141: EGOR Data::RadixTree::Shared out-of-bounds read in rdx_find_locked

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

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

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

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

Check whether you run EGOR Data::RadixTree::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-59141 · Severity: info · CVSS 0 · Published 2026-07-21

A vulnerability in a Perl library used for shared data storage allows a local attacker to crash applications or potentially read sensitive information from memory. By manipulating the data files used by the library, an attacker can cause the system to read data from incorrect locations. This could lead to service disruptions or the exposure of data belonging to other processes using the same library.

Vendors: EGOR.

Quick answers

Is CVE-2026-59141 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-59141 being exploited in the wild.
How severe is CVE-2026-59141?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: EGOR Data::RadixTree::Shared < 0.02.
Is there a fix for CVE-2026-59141?: 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-59141 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-59141?: Check whether you run EGOR Data::RadixTree::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 read vulnerability exists in Data::RadixTree::Shared before version 0.02 due to insufficient validation of node records within the rdx_find_locked function. While the rdx_validate_header function checks the header and region layout against file size, it fails to validate individual node records. A local attacker with write access to the backing file can poison node records with malicious indices. When the library performs a lookup, it may dereference these unvalidated indices, leading to an out-of-bounds read of adjacent memory or a process crash. The issue is fixed in version 0.02.

Affected products

EGOR (CPAN) Data::RadixTree::Shared < 0.02

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.