cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 44.0.0 until 50.0.0, pkcs7_decrypt_der, pkcs7_decrypt_pem, and pkcs7_decrypt_smime reported the outcome of decrypting a RecipientInfo's encryptedKey in several distinguishable ways, one of which disclosed the exact length recovered from the RSA operation. The same distinction was also observable by timing. An application that decrypts attacker-supplied EnvelopedData and reflects the outcome gives the attacker a Bleichenbacher oracle against the content-encryption key. Decryption ran as RSA PKCS#1 v1.5 decrypt of encryptedKey, build an AES cipher from the result, then AES-CBC decrypt and PKCS#7 unpad. Invalid RSA padding, a valid padding with a bad key length, a correct length with a wrong key, and the real key each failed or succeeded differently. Case 1 is reachable only where the linked library lacks implicit rejection: OpenSSL 3.0 and 3.1, LibreSSL, and BoringSSL. Exploitation requires a service that auto-decrypts untrusted EnvelopedData matching the victim certificate and answers adaptively at high volume, such as an S/MIME gateway or mail filter. This issue is fixed in 50.0.0.
CVE-2026-69247
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 7%
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 4, 2026
Advisory Details (3)
Auto-updated Aug 3, 2026commit 53fccd93413a (pyca/cryptography)
Fix landed in pyca/cryptography commit 53fccd93413a — awaiting tagged release
https://github.com/pyca/cryptography/commit/53fccd93413a8d7f07d6d8999681f27b75cffa3fDon't leak how PKCS#7 encryptedKey decryption failed
Fix merged in pyca/cryptography PR #15369 on 2026-07-31 — awaiting tagged release
https://github.com/pyca/cryptography/pull/15369PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing · Advisory · pyca/cryptography · GitHub
Affected: 50.0.0.
https://github.com/pyca/cryptography/security/advisories/GHSA-g6cj-pr64-35w5Vendor Advisories for CVE-2026-69247(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| python-cryptography | 43.0.0-3 ... 49.0.0-2 (16 versions) | — | — |
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| cryptography | 44.0.0 ... 49.0.0 (24 versions) | 50.0.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 16× in last 7d / 38× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 20:14 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 18:19 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 14:15 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:18 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:21 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 10:27 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 08:32 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 17:41 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 15:47 UTCEG score recompute
- 2026-08-11 02:50 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 00:56 UTCEG score recompute
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-08 23:02 UTCEG score recompute
Show 13 moreShow fewer
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:07 UTCEG score recompute
- 2026-08-06 19:13 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 06:16 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:20 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 14:49 UTCEG score recompute
- 2026-08-03 22:21 UTCEG score recompute
- 2026-08-03 21:38 UTCEG score recompute
- 2026-08-03 21:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-209
Frequently asked(5)
What is CVE-2026-69247?
When was CVE-2026-69247 disclosed?
Is CVE-2026-69247 actively exploited?
What is the CVSS score of CVE-2026-69247?
How do I remediate CVE-2026-69247?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69247
Is Your Infrastructure Affected by CVE-2026-69247?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.