{"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-71323 exists.","fix":"Upgrade picklescan to 0.0.33 or later.","what":"CVE-2025-71323 is a critical code injection 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-2025-71323 and fix it if it is affected.\n\nWhat it is: CVE-2025-71323 is a critical code injection 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-2025-71323 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 0.0.33\n- picklescan (PyPI): affected all versions; fixed in 0.0.33\n- picklescan (PyPI): affected all versions; fixed in 0.0.33\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-71323/ (Markdown: https://insights.sbomify.com/CVE-2025-71323/index.md)","id":"CVE-2025-71323","markdown":"https://insights.sbomify.com/CVE-2025-71323/index.md","name":"CVE-2025-71323","record":{"aliases":["GHSA-4675-36f9-wf6r","PYSEC-2026-1782"],"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 achieve remote code execution by crafting malicious pickle files that bypass picklescan's blocklist via the ctypes module.","user_interaction":"not_required","vuln_class":"code_injection"},"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-184","name":"Incomplete List of Disallowed Inputs"}],"description":"picklescan before 0.0.33 fails to block the ctypes module, allowing attackers to achieve remote code execution by invoking direct syscalls and accessing raw memory. Attackers can craft malicious pickle files using ctypes.WinDLL to load kernel32.dll and execute arbitrary commands, bypassing sandbox protections and gadget chain detection.","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 Unblocked ctypes Module","id":"CVE-2025-71323","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Flowise - Arbitrary File Read via chatId Parameter","id":"CVE-2025-71324"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.33"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-4675-36f9-wf6r"},{"ecosystem":"PyPI","fixed":["0.0.33"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-4675-36f9-wf6r"},{"ecosystem":"PyPI","fixed":["0.0.33"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-1782"}],"prev":{"headline":"PickleScan - Unsafe Globals Check Bypass via pty.spawn Function","id":"CVE-2025-71322"},"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-17","vendors":["picklescan"]},"summary":"Attackers can achieve remote code execution by crafting malicious pickle files that bypass picklescan's blocklist via the ctypes module.","url":"https://insights.sbomify.com/CVE-2025-71323/"}