pycryptodomex (pypi) has 1 known vulnerability, the worst rated HIGH. Upgrade to 3.19.1 or later to clear it. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
No published models are known to use this package.
CVSS v3.1 base score out of 10; GitHub rates it HIGH
chance of exploitation in 30 days, 50th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-j225-cvw7-qrx7, the advisory selected below
PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for pycryptodomex (pypi), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for pycryptodomex (pypi), the worst rated HIGH. They are GHSA-j225-cvw7-qrx7.
3.19.1 or later clears every advisory recorded for pycryptodomex (pypi). Check the release you pick before installing it.
Search pycryptodomex in CyberXYZ Check at https://cyberxyz.io/check?q=pycryptodomex. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:00 UTC. The most recent advisory here was published 2024-01-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.