Vulnerabilities in pkg:pypi/cryptidy
PACKAGECVE-2025-63675 is a MODERATE (CVSS 6.9) cryptidy allows code execution vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Cryptidy libraries in the PyPI ecosystem. The issue involves cryptidy allows code execution via untrusted data due to pickle.loads. Remediation is available in the latest vendor maintenance releases.
pkg:pypi/cryptidy
Vulnerability advisories affecting package pkg:pypi/cryptidy. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-97w9-v595-3h5q | CVE-2025-63675 | MODERATE | cryptidy allows code execution via untrusted data due to pickle.loads |
CVE-2025-63675 at a Glance
Security Impact
CVSS: 6.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L).
How to Fix CVE-2025-63675
To remediate this vulnerability, upgrade all affected Cryptidy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install cryptidy>=Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show cryptidy
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2025-63675, inspect your installed packages using pip:
pip show cryptidy
Analyze the terminal output to locate any version of Cryptidy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The pip show cryptidy command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Cryptidy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-63675 Affected Cryptidy Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
cryptidy
|
PyPI |
≤ 1.2.4
|
|
References
Frequently Asked Questions
What is CVE-2025-63675?
Which Cryptidy versions are affected?
What version fixes CVE-2025-63675?
Is cryptidy affected?
What is the CVSS score of CVE-2025-63675?
What CWE is associated with CVE-2025-63675?
How can I check PyPI dependencies for CVE-2025-63675?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-97w9-v595-3h5q",
"modified" : "2025-10-31T17:56:11Z",
"published" : "2025-10-31T09:30:25Z",
"aliases" : [ "CVE-2025-63675" ],
"summary" : "cryptidy allows code execution via untrusted data due to pickle.loads ",
"details" : "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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "cryptidy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.2.4"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-63675"
}, {
"type" : "WEB",
"url" : "https://github.com/javiermorales36/cryptidy-analysis"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/netinvent/cryptidy"
}, {
"type" : "WEB",
"url" : "https://github.com/netinvent/cryptidy/blob/cebc9ffd54cc20679d15a1a43ca9a5da645b0c58/cryptidy/symmetric_encryption.py#L220-L238"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-502" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2025-10-31T17:56:11Z",
"nvd_published_at" : "2025-10-31T07:15:38Z"
}
}