{"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-53873 exists.","fix":"Upgrade picklescan to 1.0.4 or later.","what":"CVE-2026-53873 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-2026-53873 and fix it if it is affected.\n\nWhat it is: CVE-2026-53873 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-2026-53873 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 1.0.4\n- picklescan (PyPI): affected all versions; fixed in 1.0.4\n- picklescan (PyPI): affected all versions; fixed in 1.0.4\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-53873/ (Markdown: https://insights.sbomify.com/CVE-2026-53873/index.md)","id":"CVE-2026-53873","markdown":"https://insights.sbomify.com/CVE-2026-53873/index.md","name":"CVE-2026-53873","record":{"aliases":["GHSA-7wx9-6375-f5wh","PYSEC-2026-455"],"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 bypassing picklescan's blocklist using the profile.run() function in malicious pickle files.","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 1.0.4 contains an incomplete blocklist for the profile module that fails to block the module-level profile.run() function, allowing attackers to achieve arbitrary code execution via exec(). Attackers can craft malicious pickle files calling profile.run(statement) to execute arbitrary Python code while picklescan reports zero security issues.","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 profile.run() Blocklist Bypass","id":"CVE-2026-53873","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"picklescan - Arbitrary Code Execution via Obfuscated eval Call","id":"CVE-2026-53874"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-7wx9-6375-f5wh"},{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-7wx9-6375-f5wh"},{"ecosystem":"PyPI","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-455"}],"prev":{"headline":"picklescan - Arbitrary File Read via Unsafe Pickle Deserialization","id":"CVE-2026-53872"},"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 execute arbitrary code by bypassing picklescan's blocklist using the profile.run() function in malicious pickle files.","url":"https://insights.sbomify.com/CVE-2026-53873/"}