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.3% (18th percentile of EPSS-scored CVEs). 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.3%CVSS: 8.2Exploit: None knownExposed services: Not assessed

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.2HIGHmedium confidence
EG Risk
37
EG Risk 37/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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

Vendor Advisories for CVE-2026-69247(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupython3-cryptography (46.0.5-1ubuntu2.2) @ resolute2026-10-04ubuntu
redhatrhaii/vllm-cpu-rhel9:17900757932026-09-23redhat
redhatrhaii/vllm-spyre-rhel9:17900761412026-09-23redhat
redhatrhaii/vllm-cuda-rhel9:17900901312026-09-23redhat
redhatrhaii/vllm-rocm-rhel9:17901096202026-09-23redhat
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 rangeFix by version rangeDependents
python-cryptography43.0.0-3 ... 49.0.0-1~exp1 (15 versions)
  • every version up to 49.0.0-2: fixed in 49.0.0-2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
cryptography44.0.0 ... 49.0.0 (24 versions)
  • 44.0.0 up to 50.0.0: fixed in 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 19× in last 7d / 81× 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.

Showing the most recent 100 of 143 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69247?
CVE-2026-69247 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69247?
A fix for CVE-2026-69247 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69247 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs