{"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-53875 exists.","fix":"Upgrade picklescan to 1.0.3 or later.","what":"CVE-2026-53875 is a high-severity code injection vulnerability in picklescan, published on 17 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-2026-53875 and fix it if it is affected.\n\nWhat it is: CVE-2026-53875 is a high-severity code injection vulnerability in picklescan, published on 17 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-2026-53875 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 1.0.3\n- picklescan (PyPI): affected all versions; fixed in 1.0.3\n- picklescan (PyPI): affected all versions; fixed in 1.0.3\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-53875/ (Markdown: https://insights.sbomify.com/CVE-2026-53875/index.md)","id":"CVE-2026-53875","markdown":"https://insights.sbomify.com/CVE-2026-53875/index.md","name":"CVE-2026-53875","record":{"aliases":["GHSA-97f8-7cmv-76j2","PYSEC-2026-2873"],"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 dynamic eval tricks to execute arbitrary code via malicious PyTorch payloads.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"}],"description":"picklescan before 1.0.3 contains a scanning bypass vulnerability in the scan_pytorch function that allows attackers to embed malicious magic numbers via dynamic eval using the __reduce__ trick. Attackers can craft malicious PyTorch payloads that evade picklescan detection while remaining executable, enabling arbitrary code execution when loaded with torch.load().","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 - Scanning Bypass via Dynamic Eval in scan_pytorch","id":"CVE-2026-53875","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Command injection in RadiX AX6600 WiFi 6 Tri-Band Gaming Router","id":"CVE-2026-53876"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-97f8-7cmv-76j2"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-97f8-7cmv-76j2"},{"ecosystem":"PyPI","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-2873"}],"prev":{"headline":"picklescan - Arbitrary Code Execution via Obfuscated eval Call","id":"CVE-2026-53874"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-17","vendors":["picklescan"]},"summary":"Attackers can bypass picklescan detection using dynamic eval tricks to execute arbitrary code via malicious PyTorch payloads.","url":"https://insights.sbomify.com/CVE-2026-53875/"}