{"answers":{"affected":"3 open source packages ship an affected version, including picklescan.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53874 exists.","fix":"Upgrade picklescan to 1.0.1 or later.","what":"CVE-2026-53874 is a critical unsafe deserialization vulnerability in picklescan, published on 17 Jun 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-53874 and fix it if it is affected.\n\nWhat it is: CVE-2026-53874 is a critical unsafe deserialization vulnerability in picklescan, published on 17 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53874 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 1.0.1\n- picklescan (PyPI): affected all versions; fixed in 1.0.1\n- picklescan (PyPI): affected all versions; fixed in 1.0.1\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-53874/ (Markdown: https://insights.sbomify.com/CVE-2026-53874/index.md)","id":"CVE-2026-53874","markdown":"https://insights.sbomify.com/CVE-2026-53874/index.md","name":"CVE-2026-53874","record":{"aliases":["GHSA-9m3x-qqw2-h32h","PYSEC-2026-1789"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python pickle scanner","requires_auth":"none","summary":"Attackers can execute arbitrary code by crafting malicious pickle files that evade detection in the picklescan library.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"picklescan before 1.0.1 contains an unsafe deserialization vulnerability allowing unauthenticated users to execute arbitrary code by hiding eval calls nested under callable objects via getattr. Attackers can embed malicious code in pickle files that evades detection but executes when the pickle is loaded from untrusted sources.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"picklescan - Arbitrary Code Execution via Obfuscated eval Call","id":"CVE-2026-53874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"picklescan - Scanning Bypass via Dynamic Eval in scan_pytorch","id":"CVE-2026-53875"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-9m3x-qqw2-h32h"},{"ecosystem":"PyPI","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-9m3x-qqw2-h32h"},{"ecosystem":"PyPI","fixed":["1.0.1"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-1789"}],"prev":{"headline":"picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass","id":"CVE-2026-53873"},"products":["picklescan"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-23","vendors":["picklescan"]},"summary":"Attackers can execute arbitrary code by crafting malicious pickle files that evade detection in the picklescan library.","url":"https://insights.sbomify.com/CVE-2026-53874/"}