{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59142 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59142 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59142 is a critical memory corruption vulnerability in EGOR Data::HashMap::Shared, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59142 and fix it if it is affected.\n\nWhat it is: CVE-2026-59142 is a critical memory corruption vulnerability in EGOR Data::HashMap::Shared, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59142 in the wild and no public exploit code.\n\nAffected product: EGOR Data::HashMap::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-59142/ (Markdown: https://insights.sbomify.com/CVE-2026-59142/index.md)","id":"CVE-2026-59142","markdown":"https://insights.sbomify.com/CVE-2026-59142/index.md","name":"CVE-2026-59142","record":{"aliases":["GHSA-4m33-8fcc-g5rp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl shared hash library","requires_auth":"none","summary":"A local attacker can trigger an out-of-bounds read in the Perl Data::HashMap::Shared library by manipulating the backing file, causing crashes or memory disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Data::HashMap::Shared versions before 0.14 for Perl allow an out-of-bounds read via an unvalidated arena offset and length in shm_str_copy.\n\nThe attach-time validator shm_validate_header checks the header scalars and region layout against the file size, but does not validate the array contents it then trusts. shm_str_copy does memcpy(dst, arena + off, len) with off and len read raw from the mmap'd segment and unbounded, on the each, keys, values, pop, shift, take, swap, drain and cursor paths. The get path bounds off and len separately and is not affected.\n\nA local peer that can write the backing file can leave the header valid while poisoning a record's offset and length, so iterating or draining the map copies a file-controlled offset and length out of the arena, reading adjacent 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::HashMap::Shared","id":"CVE-2026-59142","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::RoaringBitmap::Shared","id":"CVE-2026-59143"},"packages":[],"prev":{"headline":"Memory corruption in Data::RadixTree::Shared","id":"CVE-2026-59141"},"products":["Data::HashMap::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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["EGOR"]},"summary":"A local attacker can trigger an out-of-bounds read in the Perl Data::HashMap::Shared library by manipulating the backing file, causing crashes or memory disclosure.","url":"https://insights.sbomify.com/CVE-2026-59142/"}