{"answers":{"affected":"3 open source packages ship an affected version, including fickling. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22608 exists.","fix":"Upgrade fickling to 0.1.7 or later.","what":"CVE-2026-22608 is a high-severity unsafe deserialization vulnerability in trailofbits fickling, published on 10 Jan 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-22608 and fix it if it is affected.\n\nWhat it is: CVE-2026-22608 is a high-severity unsafe deserialization vulnerability in trailofbits fickling, published on 10 Jan 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-22608 exists.\n\nAffected packages and fixed versions:\n- fickling (PyPI): affected all versions; fixed in 0.1.7\n- fickling (PyPI): affected all versions; fixed in 0.1.7\n- fickling (PyPI): affected all versions; fixed in 0.1.7\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-22608/ (Markdown: https://insights.sbomify.com/CVE-2026-22608/index.md)","id":"CVE-2026-22608","markdown":"https://insights.sbomify.com/CVE-2026-22608/index.md","name":"CVE-2026-22608","record":{"aliases":["GHSA-5hvc-6wx8-mvv4","PYSEC-2026-1369"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python pickle analyzer","requires_auth":"none","summary":"Attackers can achieve remote code execution by chaining ctypes and pydoc gadgets, bypassing the security checks of the Fickling static analyzer.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fickling","vendor":"trailofbits"}],"cvss":{"score":8.9,"severity":"high","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/E:P","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-184","name":"Incomplete List of Disallowed Inputs"}],"description":"Fickling is a Python pickling decompiler and static analyzer. Prior to version 0.1.7, both ctypes and pydoc modules aren't explicitly blocked. Even other existing pickle scanning tools (like picklescan) do not block pydoc.locate. Chaining these two together can achieve RCE while the scanner still reports the file as LIKELY_SAFE. This issue has been patched in version 0.1.7.","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":"Fickling vulnerable to use of ctypes and pydoc gadget chain to bypass detection","id":"CVE-2026-22608","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist","id":"CVE-2026-22609"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":null,"source":"GHSA-5hvc-6wx8-mvv4"},{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":"pkg:pypi/fickling","source":"GHSA-5hvc-6wx8-mvv4"},{"ecosystem":"PyPI","fixed":["0.1.7"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":"pkg:pypi/fickling","source":"PYSEC-2026-1369"}],"prev":{"headline":"Fickling Blocklist Bypass: cProfile.run()","id":"CVE-2026-22607"},"products":["fickling"],"published":"2026-01-10","related":[{"cvss_score":8.9,"headline":"Fickling has a bypass via runpy.run_path() and runpy.run_module()","id":"CVE-2026-22606","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.9,"headline":"Fickling Blocklist Bypass: cProfile.run()","id":"CVE-2026-22607","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.9,"headline":"Fickling has Static Analysis Bypass via Incomplete Dangerous Module Blocklist","id":"CVE-2026-22609","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.9,"headline":"Fickling vulnerable to detection bypass due to \"builtins\" blindness","id":"CVE-2026-22612","kev_date_added":null,"published":"2026-01-10"},{"cvss_score":8.8,"headline":"Fickling check_safety() bypass via unlisted standard library modules (_posixsubprocess, site, atexit)","id":"CVE-2026-14534","kev_date_added":null,"published":"2026-07-04"},{"cvss_score":8.8,"headline":"Fickling MLAllowlist analysis pass rendered inoperative by shared mutable state in AnalysisContext.shorten_code()","id":"CVE-2026-14535","kev_date_added":null,"published":"2026-07-04"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-01-13","vendors":["trailofbits"]},"summary":"Attackers can achieve remote code execution by chaining ctypes and pydoc gadgets, bypassing the security checks of the Fickling static analyzer.","url":"https://insights.sbomify.com/CVE-2026-22608/"}