CVE-2026-69247

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity82% × 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

September 10, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_pr, github_commit.
github_commit

commit 53fccd93413a (pyca/cryptography)

Fix landed in pyca/cryptography commit 53fccd93413a — awaiting tagged release

https://github.com/pyca/cryptography/commit/53fccd93413a8d7f07d6d8999681f27b75cffa3f
github_pr

Don'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/15369
github Patch Available

PKCS#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-35w5

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-09-18ubuntu
redhatpython-cryptography-main-50.0.0-1.hum12026-08-17redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-cryptography43.0.0-3 ... 49.0.0-1~exp1 (15 versions)49.0.0-2
PyPI(1)
PackageVulnerable rangeFixed inDependents
cryptography44.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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 63× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 18:23 UTCVendor advisory
  3. 2026-09-18 05:16 UTCEG score recompute
  4. 2026-09-18 05:16 UTCVendor advisory
  5. 2026-09-17 16:18 UTCVendor advisory
  6. 2026-09-17 01:13 UTCEG score recompute
  7. 2026-09-17 01:13 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:18 UTCEG score recompute
  10. 2026-09-16 05:18 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 07:00 UTCEG score recompute
  13. 2026-09-15 07:00 UTCVendor advisory
  14. 2026-09-14 17:13 UTCVendor advisory
  15. 2026-09-14 04:16 UTCEG score recompute
  16. 2026-09-14 04:16 UTCVendor advisory
  17. 2026-09-13 15:19 UTCVendor advisory
  18. 2026-09-13 02:22 UTCEG score recompute
  19. 2026-09-13 02:22 UTCVendor advisory
  20. 2026-09-12 13:23 UTCVendor advisory
  21. 2026-09-12 00:25 UTCEG score recompute
  22. 2026-09-12 00:25 UTCVendor advisory
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 09:37 UTCEPSS rescore
  25. 2026-09-11 09:36 UTCVendor advisory
Show 75 more
  1. 2026-09-10 20:38 UTCEG score recompute
  2. 2026-09-10 20:38 UTCVendor advisory
  3. 2026-09-10 08:49 UTCVendor advisory
  4. 2026-09-09 19:39 UTCVendor advisory
  5. 2026-09-09 06:42 UTCEG score recompute
  6. 2026-09-09 06:42 UTCVendor advisory
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 18:46 UTCEG score recompute
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 20:39 UTCEG score recompute
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-05 18:41 UTCEG score recompute
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-04 16:47 UTCEG score recompute
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-03 08:31 UTCEG score recompute
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 20:57 UTCEG score recompute
  19. 2026-09-01 13:54 UTCEPSS rescore
  20. 2026-09-01 04:40 UTCEPSS rescore
  21. 2026-08-30 23:50 UTCEG score recompute
  22. 2026-08-30 19:17 UTCEPSS rescore
  23. 2026-08-30 10:53 UTCEG score recompute
  24. 2026-08-30 01:22 UTCEPSS rescore
  25. 2026-08-29 21:56 UTCEG score recompute
  26. 2026-08-28 21:42 UTCEPSS rescore
  27. 2026-08-27 23:45 UTCEG score recompute
  28. 2026-08-26 21:39 UTCEG score recompute
  29. 2026-08-26 14:47 UTCEPSS rescore
  30. 2026-08-25 19:39 UTCEG score recompute
  31. 2026-08-25 13:49 UTCEPSS rescore
  32. 2026-08-24 17:44 UTCEG score recompute
  33. 2026-08-23 02:19 UTCEG score recompute
  34. 2026-08-23 00:19 UTCEPSS rescore
  35. 2026-08-22 00:25 UTCEG score recompute
  36. 2026-08-21 23:49 UTCEPSS rescore
  37. 2026-08-21 11:27 UTCEG score recompute
  38. 2026-08-20 22:56 UTCEPSS rescore
  39. 2026-08-19 20:14 UTCEG score recompute
  40. 2026-08-19 17:04 UTCEPSS rescore
  41. 2026-08-18 18:19 UTCEG score recompute
  42. 2026-08-18 13:49 UTCEPSS rescore
  43. 2026-08-18 13:49 UTCEPSS rescore
  44. 2026-08-17 14:15 UTCEG score recompute
  45. 2026-08-17 13:47 UTCEPSS rescore
  46. 2026-08-17 01:18 UTCEG score recompute
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 14:56 UTCEPSS rescore
  49. 2026-08-16 12:21 UTCEG score recompute
  50. 2026-08-16 02:15 UTCEPSS rescore
  51. 2026-08-15 10:27 UTCEG score recompute
  52. 2026-08-15 01:30 UTCEPSS rescore
  53. 2026-08-14 08:32 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescore
  55. 2026-08-12 17:41 UTCEG score recompute
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-11 15:47 UTCEG score recompute
  58. 2026-08-11 02:50 UTCEG score recompute
  59. 2026-08-11 00:00 UTCEPSS rescore
  60. 2026-08-10 00:56 UTCEG score recompute
  61. 2026-08-09 13:47 UTCEPSS rescore
  62. 2026-08-08 23:02 UTCEG score recompute
  63. 2026-08-08 16:37 UTCEPSS rescore
  64. 2026-08-07 21:07 UTCEG score recompute
  65. 2026-08-06 19:13 UTCEG score recompute
  66. 2026-08-06 13:47 UTCEPSS rescore
  67. 2026-08-06 06:16 UTCEG score recompute
  68. 2026-08-05 19:17 UTCEPSS rescore
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-04 15:20 UTCEG score recompute
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 14:49 UTCEG score recompute
  73. 2026-08-03 22:21 UTCEG score recompute
  74. 2026-08-03 21:38 UTCEG score recompute
  75. 2026-08-03 21:38 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-69247?
CVE-2026-69247 is a high vulnerability published on August 3, 2026. cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 44.0.0 until 50.0.0, pkcs7decryptder, pkcs7decryptpem, and pkcs7decryptsmime reported the outcome of decrypting a RecipientInfo's encryptedKey in several distinguishable ways, one of which…
When was CVE-2026-69247 disclosed?
CVE-2026-69247 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69247 actively exploited?
CVE-2026-69247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
What is the CVSS score of CVE-2026-69247?
CVE-2026-69247 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-69247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69247, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-69247

Explore →

Is Your Infrastructure Affected by CVE-2026-69247?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.