{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-59147 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59147 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59147 is a critical memory corruption vulnerability in EGOR Data::DisjointSet::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-59147 and fix it if it is affected.\n\nWhat it is: CVE-2026-59147 is a critical memory corruption vulnerability in EGOR Data::DisjointSet::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-59147 in the wild and no public exploit code.\n\nAffected product: EGOR Data::DisjointSet::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-59147/ (Markdown: https://insights.sbomify.com/CVE-2026-59147/index.md)","id":"CVE-2026-59147","markdown":"https://insights.sbomify.com/CVE-2026-59147/index.md","name":"CVE-2026-59147","record":{"aliases":["GHSA-2q6p-wjf6-872r"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl DisjointSet library","requires_auth":"none","summary":"A local attacker can corrupt memory or crash the application by providing a malicious backing file to the Perl Data::DisjointSet::Shared library.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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::DisjointSet::Shared versions before 0.02 for Perl allow out-of-bounds reads and writes via an unvalidated parent index in dsu_find.\n\nThe attach-time validator dsu_validate_header checks the header scalars and region layout against the file size, but does not validate the array contents it then trusts. dsu_find walks and path-compresses parent[x] with x a raw file-stored index never bounded against the node count, so both the read and the compression write-back land out of bounds.\n\nA local peer that can write the backing file can leave the header valid while poisoning the parent array, so the next find or union both reads and writes through an out-of-bounds parent index, 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::DisjointSet::Shared","id":"CVE-2026-59147","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":"Mockoon: Unauthenticated admin API + wildcard CORS allows mock-state hijack and secret theft","id":"CVE-2026-59148"},"packages":[],"prev":{"headline":"Memory corruption in Data::SpatialHash::Shared","id":"CVE-2026-59146"},"products":["Data::DisjointSet::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":"total"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["EGOR"]},"summary":"A local attacker can corrupt memory or crash the application by providing a malicious backing file to the Perl Data::DisjointSet::Shared library.","url":"https://insights.sbomify.com/CVE-2026-59147/"}