{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-1889 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-1889 is a medium-severity vulnerability in mmaitre314 picklescan, published on 3 Mar 2025. 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-2025-1889 and fix it if it is affected.\n\nWhat it is: CVE-2025-1889 is a medium-severity vulnerability in mmaitre314 picklescan, published on 3 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-1889 in the wild and no public exploit code.\n\nAffected product: mmaitre314 picklescan. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-1889/ (Markdown: https://insights.sbomify.com/CVE-2025-1889/index.md)","id":"CVE-2025-1889","markdown":"https://insights.sbomify.com/CVE-2025-1889/index.md","name":"CVE-2025-1889","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python security scanner","requires_auth":"none","summary":"Attackers can bypass picklescan security checks by using non-standard file extensions for malicious pickle files, allowing unsafe models to pass validation.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Sonatype","cpe":[{"product":"picklescan","vendor":"mmaitre314"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-646","name":"Reliance on File Name or Extension of Externally-Supplied File"}],"description":"picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"picklescan - Security scanning bypass via non-standard file extensions","id":"CVE-2025-1889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"shishuocms ManageUpLoadAction.java handleRequest unrestricted upload","id":"CVE-2025-1890"},"packages":[],"prev":{"headline":"Reflected Cross Site Scripting in Aperio Eslide Manager","id":"CVE-2025-1888"},"products":["picklescan"],"published":"2025-03-03","related":[{"cvss_score":9.3,"headline":"PickleScan Security Bypass Using Misleading File Extension","id":"CVE-2025-10155","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":9.3,"headline":"PickleScan Security Bypass via Bad CRC in ZIP Archive","id":"CVE-2025-10156","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":9.3,"headline":"PickleScan Bypasses Unsafe Globals Check Using Submodule Imports","id":"CVE-2025-10157","kev_date_added":null,"published":"2025-09-17"},{"cvss_score":7.6,"headline":"picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass","id":"CVE-2025-71348","kev_date_added":null,"published":"2026-06-21"},{"cvss_score":7.6,"headline":"picklescan - Arbitrary Code Execution via Undetected idlelib.pyshell.ModifiedInterpreter.runcommand","id":"CVE-2025-71357","kev_date_added":null,"published":"2026-06-21"},{"cvss_score":7.6,"headline":"picklescan - Remote Code Execution via Undetected cProfile.runctx in Pickle Files","id":"CVE-2025-71378","kev_date_added":null,"published":"2026-06-21"},{"cvss_score":6.9,"headline":"picklescan - Arbitrary File Creation via logging.FileHandler Deserialization","id":"CVE-2026-56304","kev_date_added":null,"published":"2026-06-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["mmaitre314"]},"summary":"Attackers can bypass picklescan security checks by using non-standard file extensions for malicious pickle files, allowing unsafe models to pass validation.","url":"https://insights.sbomify.com/CVE-2025-1889/"}