Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-69247Published 2026-08-03

CVE-2026-69247 — pyca cryptography

high (derived)

As of 2026-08-03, CVE-2026-69247 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in pyca cryptography, CVSS v4.0 8.2. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-69247 as of 2026-08-03; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
8.2/10High (derived)
EPSS
—No EPSS score yet
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.1/10Threadlinqs triage score
Published
CVSS v4.0 8.2 (High, derived from score) · Priority 4.1/10 · Published 2026-08-03

Last updated:

What is CVE-2026-69247?

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.

The record classifies CVE-2026-69247 under weakness classes CWE-208, CWE-209. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 63 days ago.

Severity and exploitation probability

CVSS v4.0 base score
8.2 — High (derived from score)
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.1/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-03

Is CVE-2026-69247 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

  • pyca: cryptography

Affected software packages:

  • pip:cryptography — patched in 50.0.0

How to fix CVE-2026-69247

Fixed versions are recorded for 1 package: pip:cryptography 50.0.0. No vendor patch reference has been recorded for CVE-2026-69247 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-69247

No threat campaign in the Threadlinqs corpus currently references CVE-2026-69247, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, GitHub Security Advisories. Last verified by Threadlinqs on .

Vendor advisory and patch

Other references