{"answers":{"affected":"3 open source packages ship an affected version, including cryptidy. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63675 exists.","fix":"No fix has been published for CVE-2025-63675 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-63675 is a medium-severity unsafe deserialization vulnerability in cryptidy, published on 31 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-63675 and fix it if it is affected.\n\nWhat it is: CVE-2025-63675 is a medium-severity unsafe deserialization vulnerability in cryptidy, published on 31 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63675 exists.\n\nAffected packages and fixed versions:\n- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed\n- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed\n- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed\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-63675/ (Markdown: https://insights.sbomify.com/CVE-2025-63675/index.md)","id":"CVE-2025-63675","markdown":"https://insights.sbomify.com/CVE-2025-63675/index.md","name":"CVE-2025-63675","record":{"aliases":["GHSA-97w9-v595-3h5q","PYSEC-2026-1282"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python cryptography library","requires_auth":"none","summary":"Attackers can execute arbitrary code by providing malicious serialized data to the cryptidy library's decryption function.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"cryptidy","vendor":"netinvent"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"cryptidy through 1.2.4 allows code execution via untrusted data because pickle.loads is used. This occurs in aes_decrypt_message in symmetric_encryption.py.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"cryptidy allows code execution via untrusted data due to pickle.loads","id":"CVE-2025-63675","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2025-63678"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.2.4"],"package":"cryptidy","purl":null,"source":"GHSA-97w9-v595-3h5q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.2.4"],"package":"cryptidy","purl":"pkg:pypi/cryptidy","source":"GHSA-97w9-v595-3h5q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.2.4"],"package":"cryptidy","purl":"pkg:pypi/cryptidy","source":"PYSEC-2026-1282"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2025-63674"},"products":["cryptidy"],"published":"2025-10-31","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":"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-10-31","vendors":["cryptidy"]},"summary":"Attackers can execute arbitrary code by providing malicious serialized data to the cryptidy library's decryption function.","url":"https://insights.sbomify.com/CVE-2025-63675/"}