CVE-2026-69247
Bleichenbacher-style padding oracle in Python cryptography pkcs7/S-MIME decryption (v44.0.0–<50.0.0)
Is CVE-2026-69247 being exploited?
Not confirmed. CVE-2026-69247 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-69247?
CVE-2026-69247 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69247?
Yes. A fix has been recorded for CVE-2026-69247. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69247 affect?
CVE-2026-69247 affects python-cryptography 44.0.0–<50.0.0, S/MIME gateways and mail filters using affected library, Applications auto-decrypting untrusted EnvelopedData. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69247?
Upgrade to cryptography >=50.0.0 and disable auto-decrypt of untrusted EnvelopedData on mail/S/MIME services.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can mount a Bleichenbacher oracle to recover RSA-encrypted content-encryption keys and decrypt AES-CBC PKCS#7/S/MIME payloads, exposing message contents.
Patch when possible
- affected>= 44.0.0 and < 50.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.