{"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-2025-67747 exists.","fix":"Upgrade fickling to 0.1.6 or later.","what":"CVE-2025-67747 is a high-severity unsafe deserialization vulnerability in trailofbits fickling, published on 16 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-67747 and fix it if it is affected.\n\nWhat it is: CVE-2025-67747 is a high-severity unsafe deserialization vulnerability in trailofbits fickling, published on 16 Dec 2025. It can only be exploited from the same machine or local network, 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-2025-67747 exists.\n\nAffected packages and fixed versions:\n- fickling (PyPI): affected all versions; fixed in 0.1.6\n- fickling (PyPI): affected all versions; fixed in 0.1.6\n- fickling (PyPI): affected all versions; fixed in 0.1.6\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-67747/ (Markdown: https://insights.sbomify.com/CVE-2025-67747/index.md)","id":"CVE-2025-67747","markdown":"https://insights.sbomify.com/CVE-2025-67747/index.md","name":"CVE-2025-67747","record":{"aliases":["GHSA-565g-hwwr-4pp3","PYSEC-2026-1368"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python pickling analyzer","requires_auth":"none","summary":"Attackers can bypass security checks in Fickling to execute arbitrary code via malicious pickle files due to missing module blocklist entries.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"fickling","vendor":"trailofbits"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/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. Versions prior to 0.1.6 are missing `marshal` and `types` from the block list of unsafe module imports. Fickling started blocking both modules to address this issue. This allows an attacker to craft a malicious pickle file that can bypass fickling since it misses detections for `types.FunctionType` and `marshal.loads`. A user who deserializes such a file, believing it to be safe, would inadvertently execute arbitrary code on their system. This impacts any user or system that uses Fickling to vet pickle files for security issues. The issue was fixed in version 0.1.6.","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 has missing detection for marshal.loads and types.FunctionType in unsafe modules list","id":"CVE-2025-67747","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"Fickling has Code Injection vulnerability via pty.spawn()","id":"CVE-2025-67748"},"packages":[{"ecosystem":"PyPI","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":null,"source":"GHSA-565g-hwwr-4pp3"},{"ecosystem":"PyPI","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":"pkg:pypi/fickling","source":"GHSA-565g-hwwr-4pp3"},{"ecosystem":"PyPI","fixed":["0.1.6"],"introduced":["0"],"last_affected":[],"package":"fickling","purl":"pkg:pypi/fickling","source":"PYSEC-2026-1368"}],"prev":{"headline":"Composer vulnerable to ANSI sequence injection","id":"CVE-2025-67746"},"products":["fickling"],"published":"2025-12-16","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 vulnerable to use of ctypes and pydoc gadget chain to bypass detection","id":"CVE-2026-22608","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-16","vendors":["trailofbits"]},"summary":"Attackers can bypass security checks in Fickling to execute arbitrary code via malicious pickle files due to missing module blocklist entries.","url":"https://insights.sbomify.com/CVE-2025-67747/"}