PyCryptodome and pycryptodomex side-channel leakage for OAEP decryptionGHSA-j225-cvw7-qrx7
MEDIUMFix: Legrandin/pycryptodome@0deea1bGHSA-j225-cvw7-qrx7 is a medium-severity (CVSS 5.3) CWE-203 vulnerability in pycryptodomex. A fix is available for pycryptodomex — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j225-cvw7-qrx7.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
pycryptodomex🐍pycryptodomeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | pycryptodomex | all versions | 3.19.1pip install --upgrade 'pycryptodomex==3.19.1' |
| 🐍PyPI | pycryptodome | all versions | 3.19.1pip install --upgrade 'pycryptodome==3.19.1' |
Affected Products
pycryptodomepycryptodomepycryptodomexpycryptodomeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pycryptodomex, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pycryptodomex to 3.19.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j225-cvw7-qrx7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Satellite ship affected version of pycryptodome for pulp_container, however, product is not vulnerable as it doesn't utilize OAEP algorithm technique. Red Hat Product Security has classified its impact as Low for Red Hat Satellite; future updates expected to address this issue. Red Hat OpenStack 16.1 and 16.2…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Ansible Automation Platform 2.4 for RHEL 8 | python3x-pycryptodomex-0:3.20.0-1.el8ap | RHSA-2024:1057 |
| Red Hat Enterprise Linux 8 | fence-agents-0:4.2.1-121.el8_9.4 | RHBA-2024:0891 |
| Red Hat Enterprise Linux 8 | fence-agents-0:4.2.1-129.el8 | RHSA-2024:2968 |
| Red Hat Enterprise Linux 8 | resource-agents-0:4.9.0-54.el8 | RHSA-2024:2952 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | fence-agents-0:4.2.1-65.el8_4.14 | RHBA-2024:1398 |
| Red Hat Enterprise Linux 8.6 Extended Update Support | fence-agents-0:4.2.1-89.el8_6.11 | RHBA-2024:1114 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | fence-agents-0:4.2.1-112.el8_8.3 | RHBA-2024:1416 |
| Red Hat Enterprise Linux 9 | fence-agents-0:4.10.0-55.el9_3.3 | RHBA-2024:1137 |
Frequently Asked Questions
Is GHSA-j225-cvw7-qrx7 in your dependencies?
Find it across PyPI, including transitive dependencies.