CVE-2025-63675

MEDIUMNVD 6.96.9—Elevated

6.9

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.

CVSS v3: 6.9
EG Score: 6.9(medium)
EPSS: 22.8%
KEV: Not listed

Published

October 31, 2025

Last Modified

December 8, 2025

References (3)

cve@mitrehttps://github.com/javiermorales36/cryptidy-analysis
cve@mitrehttps://github.com/netinvent/cryptidy/blob/cebc9ffd54cc20679d15a1a43ca9a5da645b0c58/cryptidy/symmetric_encryption.py#L220-L238
134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/javiermorales36/cryptidy-analysis

Patch Availability(1)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
pip	cryptidy	—	ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-502Deserialization of Untrusted Data

Data Freshness Timeline

(refreshed 14× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:46 UTCepss_batch
2026-06-05 22:46 UTCepss_batch
2026-06-05 06:10 UTCepss_batch
2026-06-05 06:10 UTCepss_batch
2026-06-04 13:12 UTCepss_batch
2026-06-04 13:12 UTCepss_batch
2026-06-02 20:13 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 19:57 UTCEG score recompute
2026-05-29 19:57 UTCGHSA enrichment
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2025-63675?

CVE-2025-63675 is a medium vulnerability published on October 31, 2025. cryptidy through 1.2.4 allows code execution via untrusted data because pickle.loads is used. This occurs in aesdecryptmessage in symmetric_encryption.py.

When was CVE-2025-63675 disclosed?

CVE-2025-63675 was first published in the National Vulnerability Database on October 31, 2025, with the most recent update on December 8, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2025-63675 actively exploited?

CVE-2025-63675 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2025-63675?

CVE-2025-63675 has a CVSS v3 base score of 6.9 (NVD).

How do I remediate CVE-2025-63675?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-63675, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-63675

Explore →

Is Your Infrastructure Affected by CVE-2025-63675?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2025-63675

📅 Published

🔄 Last Modified

🔗 References (3)

Patch Availability(1)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2025-63675?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (3)

Frequently asked(5)

Related CVEs(same CWE)