# CVE-2025-63675: cryptidy allows code execution via untrusted data due to pickle.loads

> Attackers can execute arbitrary code by providing malicious serialized data to the cryptidy library's decryption function.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 31 Oct 2025
- **Also known as:** GHSA-97w9-v595-3h5q, PYSEC-2026-1282

## What is CVE-2025-63675?

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.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-63675?

3 open source packages ship an affected version, including cryptidy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cryptidy` | PyPI | All versions to 1.2.4 | None |
| `cryptidy` | PyPI | All versions to 1.2.4 | None |
| `cryptidy` | PyPI | All versions to 1.2.4 | None |

Products: Netinvent Cryptidy.

## How do I fix CVE-2025-63675?

No fix has been published for CVE-2025-63675 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63675 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63675 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63675 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63675 exists.

Affected packages and fixed versions:
- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed
- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed
- cryptidy (PyPI): affected all versions up to 1.2.4; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63675/ (Markdown: https://insights.sbomify.com/CVE-2025-63675/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63675
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63675
- OSV: https://osv.dev/vulnerability/CVE-2025-63675

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63675/
Summaries are generated and may contain mistakes; the official description above is the record.