{"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-53872 exists.","fix":"Upgrade picklescan to 0.0.35 or later.","what":"CVE-2026-53872 is a high-severity unsafe deserialization 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-53872 and fix it if it is affected.\n\nWhat it is: CVE-2026-53872 is a high-severity unsafe deserialization 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-53872 exists.\n\nAffected packages and fixed versions:\n- picklescan (PyPI): affected all versions; fixed in 0.0.35\n- picklescan (PyPI): affected all versions; fixed in 0.0.35\n- picklescan (PyPI): affected all versions; fixed in 0.0.35\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-53872/ (Markdown: https://insights.sbomify.com/CVE-2026-53872/index.md)","id":"CVE-2026-53872","markdown":"https://insights.sbomify.com/CVE-2026-53872/index.md","name":"CVE-2026-53872","record":{"aliases":["GHSA-9726-w42j-3qjr","PYSEC-2026-1787"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Python pickle scanner","requires_auth":"none","summary":"Unauthenticated attackers can read arbitrary server files and exfiltrate data by exploiting unsafe pickle deserialization in picklescan.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"picklescan before 0.0.35 contains an unsafe pickle deserialization vulnerability allowing unauthenticated attackers to read arbitrary server files by chaining io.FileIO and urllib.request.urlopen. Attackers can bypass RCE-focused blocklists to exfiltrate sensitive data like /etc/passwd to external servers.","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 File Read via Unsafe Pickle Deserialization","id":"CVE-2026-53872","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"picklescan - Arbitrary Code Execution via profile.run() Blocklist Bypass","id":"CVE-2026-53873"},"packages":[{"ecosystem":"PyPI","fixed":["0.0.35"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":null,"source":"GHSA-9726-w42j-3qjr"},{"ecosystem":"PyPI","fixed":["0.0.35"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"GHSA-9726-w42j-3qjr"},{"ecosystem":"PyPI","fixed":["0.0.35"],"introduced":["0"],"last_affected":[],"package":"picklescan","purl":"pkg:pypi/picklescan","source":"PYSEC-2026-1787"}],"prev":{"headline":"Hermes WebUI \u003c 0.51.368 - Profile-Scoped Authorization Bypass via Forged hermes_profile Cookie","id":"CVE-2026-53871"},"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":"partial"},"state":"PUBLISHED","updated":"2026-06-17","vendors":["picklescan"]},"summary":"Unauthenticated attackers can read arbitrary server files and exfiltrate data by exploiting unsafe pickle deserialization in picklescan.","url":"https://insights.sbomify.com/CVE-2026-53872/"}