PatchTheCVECVE-2023-52323: PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a
CVE-2023-52323 is a medium-severity flaw (CVSS 5.9) affecting pycryptodome, pycryptodomex. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
Why this priority
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.9 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 51%) |
| CISA exploited list | No |
| Weakness | CWE-203 |
| Published | 2024-01-05 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-52323?
pycryptodome: upgrade to 3.19.1; pycryptodomex: upgrade to 3.19.1. Exact commands for each OS are on this page.
Is CVE-2023-52323 being exploited?
CVE-2023-52323 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-52323 affect?
CVE-2023-52323 affects pycryptodome, pycryptodomex. Severity is medium (CVSS 5.9). PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack.
How urgent is CVE-2023-52323?
Priority 38/100. Remotely exploitable, no login, no user action