Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
PyCryptodome and pycryptodomex before 3.19.1 leak side-channel information during OAEP decryption, which can be exploited with a Manger attack. The source gives few details about the attacker's required position or what they can recover. Upgrade pycryptodome and pycryptodomex to 3.19.1 or later.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0062, the 50th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:36 UTC First seen by agentprime
- 31 Oct 2026, 14:36 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-j225-cvw7-qrx7
- OSV: GHSA-j225-cvw7-qrx7
- nvd.nist.gov/vuln/detail/CVE-2023-52323
- github.com/Legrandin/pycryptodome/commit/0deea1bfe1489e8c80d2053bbb06a1aa0b181ebd
- github.com/Legrandin/pycryptodome
- github.com/Legrandin/pycryptodome/blob/master/Changelog.rst
- github.com/pypa/advisory-database/tree/main/vulns/pycryptodomex/PYSEC-2024-3.yaml
- pypi.org/project/pycryptodomex/#history