{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59146 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59146 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59146 is a high-severity memory corruption vulnerability in EGOR Data::SpatialHash::Shared, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59146 and fix it if it is affected.\n\nWhat it is: CVE-2026-59146 is a high-severity memory corruption vulnerability in EGOR Data::SpatialHash::Shared, published on 21 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-59146 in the wild and no public exploit code.\n\nAffected product: EGOR Data::SpatialHash::Shared. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59146/ (Markdown: https://insights.sbomify.com/CVE-2026-59146/index.md)","id":"CVE-2026-59146","markdown":"https://insights.sbomify.com/CVE-2026-59146/index.md","name":"CVE-2026-59146","record":{"aliases":["GHSA-p5xm-h38r-4xmg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Perl spatial hash library","requires_auth":"none","summary":"A local attacker with file write access can trigger out-of-bounds reads and writes in the Perl Data::SpatialHash::Shared library, leading to memory corruption or crashes.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Data::SpatialHash::Shared versions before 0.02 for Perl allow out-of-bounds reads and writes via unvalidated bucket, link and free-list indices in sph_walk_cell and sph_alloc_slot.\n\nThe attach-time validator sph_validate_header checks the header scalars and region layout against the file size, but does not validate the array contents it then trusts. sph_walk_cell reads entries[buckets[b]] and follows each entry's next link raw, and sph_alloc_slot writes through a file-stored free_head index, none bounded against the entry count (max_entries).\n\nA local peer that can write the backing file can leave the header valid while poisoning the bucket chain and free list, so a query reads through an out-of-bounds bucket and next index and an insert writes through an out-of-bounds free-list head, corrupting memory or crashing the process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in Data::SpatialHash::Shared","id":"CVE-2026-59146","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Data::DisjointSet::Shared","id":"CVE-2026-59147"},"packages":[],"prev":{"headline":"Information disclosure in Data::Intern::Shared","id":"CVE-2026-59145"},"products":["Data::SpatialHash::Shared"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["EGOR"]},"summary":"A local attacker with file write access can trigger out-of-bounds reads and writes in the Perl Data::SpatialHash::Shared library, leading to memory corruption or crashes.","url":"https://insights.sbomify.com/CVE-2026-59146/"}