Memory corruption via unvalidated shared-file indices
Published Jul 21, 2026 · Updated Jul 21, 2026
Out-of-bounds access in Data::SpatialHash::Shared before 0.02 allows local users to corrupt memory or crash a Perl process. sph_validate_header accepts array contents without bounds checks, so sph_walk_cell dereferences poisoned bucket and next indices and sph_alloc_slot writes through a poisoned free_head index. Exploitation requires write access to a valid backing file and subsequent use of a poisoned chain or free list by the target process.
Summary
What happened
Out-of-bounds access in Data::SpatialHash::Shared before 0.02 allows local users to corrupt memory or crash a Perl process. sph_validate_header accepts array contents without bounds checks, so sph_walk_cell dereferences poisoned bucket and next indices and sph_alloc_slot writes through a poisoned free_head index. Exploitation requires write access to a valid backing file and subsequent use of a poisoned chain or free list by the target process.
The record
- CVE
- CVE-2026-59146
- Published
- Jul 21, 2026
- Updated
- Jul 21, 2026
- Vendor
- Yegor Korablev
- Product
- Data::SpatialHash::Shared
- Classifications
- CWE-125, CWE-787, T1565.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2026CVE publishedPublication date reported by the CVE source.
- Jul 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.02
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo