{"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-2025-71351 exists.","fix":"Upgrade picklescan to 0.0.25 or later.","what":"CVE-2025-71351 is a high-severity unsafe deserialization vulnerability in picklescan, published on 21 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-71351 and fix it if it is affected.\n\nWhat it is: CVE-2025-71351 is a high-severity unsafe deserialization vulnerability in picklescan, published on 21 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-71351 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 0.0.25\n- picklescan (PyPI): affected all versions; fixed in 0.0.25\n- picklescan (PyPI): affected all versions; fixed in 0.0.25\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-2025-71351/ (Markdown: https://insights.sbomify.com/CVE-2025-71351/index.md)","id":"CVE-2025-71351","markdown":"https://insights.sbomify.com/CVE-2025-71351/index.md","name":"CVE-2025-71351","record":{"aliases":["GHSA-v7x6-rv5q-mhwc","PYSEC-2026-4135"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python security library","requires_auth":"none","summary":"Attackers can bypass picklescan detection using timeit.timeit() in pickle files to achieve remote code execution when the library processes malicious data.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"picklescan before 0.0.25 fails to detect malicious pickle files that use timeit.timeit() in the __reduce__ method, allowing remote code execution. Attackers can craft pickle files that import dangerous libraries like os and execute arbitrary system commands, which evade picklescan detection and execute when pickle.load() is called.","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 - Remote Code Execution via timeit.timeit() Detection Bypass","id":"CVE-2025-71351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"picklescan - Remote Code Execution via Undetected trace.Trace.runctx in Pickle Files","id":"CVE-2025-71352"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.25"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-v7x6-rv5q-mhwc"},{"ecosystem":"PyPI","fixed":["0.0.25"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-v7x6-rv5q-mhwc"},{"ecosystem":"PyPI","fixed":["0.0.25"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-4135"}],"prev":{"headline":"picklescan - Undetected Remote Code Execution via torch.utils.collect_env.run","id":"CVE-2025-71350"},"products":["picklescan"],"published":"2026-06-21","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["picklescan"]},"summary":"Attackers can bypass picklescan detection using timeit.timeit() in pickle files to achieve remote code execution when the library processes malicious data.","url":"https://insights.sbomify.com/CVE-2025-71351/"}