{"answers":{"affected":"2 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-71363 exists.","fix":"Upgrade picklescan to 0.0.30 or later.","what":"CVE-2025-71363 is a high-severity unsafe deserialization vulnerability in picklescan, published on 30 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-71363 and fix it if it is affected.\n\nWhat it is: CVE-2025-71363 is a high-severity unsafe deserialization vulnerability in picklescan, published on 30 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-71363 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 0.0.30\n- picklescan (PyPI): affected all versions; fixed in 0.0.30\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-71363/ (Markdown: https://insights.sbomify.com/CVE-2025-71363/index.md)","id":"CVE-2025-71363","markdown":"https://insights.sbomify.com/CVE-2025-71363/index.md","name":"CVE-2025-71363","record":{"aliases":["GHSA-49gj-c84q-6qm9","GHSA-r9rj-xr26-286v"],"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 bypass picklescan's detection of cProfile.run calls.","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-502","name":"Deserialization of Untrusted Data"}],"description":"picklescan before 0.0.30 fails to detect cProfile.run function calls in pickle reduce methods, allowing attackers to execute arbitrary code. Remote attackers can craft malicious pickle files with cProfile.run payloads that bypass picklescan detection and achieve code execution upon deserialization.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"picklescan - Arbitrary Code Execution via Undetected cProfile.run in Pickle Deserialization","id":"CVE-2025-71363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"picklescan - Arbitrary Code Execution via Undetected asyncio.unix_events._UnixSubprocessTransport._start","id":"CVE-2025-71364"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.30"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-49gj-c84q-6qm9"},{"ecosystem":"PyPI","fixed":["0.0.30"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-49gj-c84q-6qm9"}],"prev":{"headline":"picklescan - Arbitrary Code Execution via Unsafe Deserialization in numpy.f2py.crackfortran","id":"CVE-2025-71362"},"products":["picklescan"],"published":"2026-06-30","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":"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-07-01","vendors":["picklescan"]},"summary":"Attackers can execute arbitrary code by crafting malicious pickle files that bypass picklescan's detection of cProfile.run calls.","url":"https://insights.sbomify.com/CVE-2025-71363/"}