BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-69247High confidence

cryptography: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing

pyca · cryptography

Official source article: GitHub GHSA-G6CJ-PR64-35W5 ↗. Check the applicable product and release in the original source.

8.2HighCVSS 4.0
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.27% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs pyca cryptography and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepython-cryptographyNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian bookwormbookworm · sourcepython-cryptographyNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 8 Oct 2026
Debian forkyforky · sourcepython-cryptographyVendor fix publishedDebian records a fixed source-package version for this release.49.0.0-2Debian Security Tracker ↗Source updated 8 Oct 2026
Debian sidsid · sourcepython-cryptographyVendor fix publishedDebian records a fixed source-package version for this release.49.0.0-2Debian Security Tracker ↗Source updated 8 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIcryptographyECOSYSTEM: introduced 44.0.0; fixed 50.0.050.0.0OSV record ↗aggregator derived · 10 Sep 2026
pipcryptography>= 44.0.0, < 50.0.050.0.0GitHub advisory ↗upstream repository advisory · 3 Aug 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-69247 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypython-cryptography: python-cryptography: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python3-cryptography as a component of Red Hat Enterprise Linux 10
  • python3.14-cryptography as a component of Red Hat Enterprise Linux 10
  • python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10
  • python3.14-cryptography as a component of Red Hat Enterprise Linux 9
  • python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in cryptography, a Python package for cryptographic primitives. This vulnerability, known as a Bleichenbacher oracle, arises during PKCS#7 EnvelopedData decryption. An attacker can exploit distinguishable error messages and timing differences during decryption to gain information about the content-encryption key. Exploitation requires a high-volume service, such as an S/MIME gateway, that automatically decrypts untrusted data matching a victim's certificate. Successful exploitation could lead to the disclosure of sensitive encryption keys, allowing an attacker to decrypt confidential communications.
Remediation
For more information visit https://access.redhat.com/errata/RHSA-2026:70965
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-52446

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

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.

What

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.

Why

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Observable Timing Discrepancy → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-208 ↗

CWE-208: Observable Timing Discrepancy. Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-208
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 Aug 2026, published on 5 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2026-6653 Référence CVE CVE-2026-6791 https://www.cve.org/CVERecord?id=CVE-2026-6791 Référence CVE CVE-2026-68497 https://www.cve.org/CVERecord?id=CVE-2026-68497 Référence CVE CVE-2026-68525 https://www.cve.org/CVERecord?id=CVE-2026-68525 Référence CVE CVE-2026-68569 https://www.cve.org/CVERecord?id=CVE-2026-68569 Référence CVE CVE-2026-68763 https://www.cve.org/CVERecord?id=CVE-2026-68763 Référence CVE CVE-2026-6879 https://www.cve.org/CVERecord?id=CVE-2026-6879 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69192 https://www.cve.org/CVERecord?id=CVE-2026-69192 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-73180 https://www.cve.org/CVERecord?id=CVE-2026-73180 Référence CVE CVE-2026-7383 https://www.cve.org/CVERecord?id=CVE-2026-7383 Référence CVE CVE-2026-75595 https://www.cve.org/CVERecord?id=CVE-2026-75595 Référence CVE CVE-2026-75596 https://www.cve.org/CVERecord?id=CVE-2026-75596 Référence CVE CVE-2026-75803 https://www.cve.org/CVERecord?id=CVE-2026-75803 Référence CVE CVE-2026-77117 https://www.cve.org/CVERecord?id=CVE-2026-77117 Référence CVE CVE-2026-77310 https://www.cve.org/CVERecord?id=CVE-2026-77310 Référence CVE CVE-2026-80489 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-63388 Référence CVE CVE-2026-63495 https://www.cve.org/CVERecord?id=CVE-2026-63495 Référence CVE CVE-2026-6402 https://www.cve.org/CVERecord?id=CVE-2026-6402 Référence CVE CVE-2026-6429 https://www.cve.org/CVERecord?id=CVE-2026-6429 Référence CVE CVE-2026-66010 https://www.cve.org/CVERecord?id=CVE-2026-66010 Référence CVE CVE-2026-67213 https://www.cve.org/CVERecord?id=CVE-2026-67213 Référence CVE CVE-2026-67214 https://www.cve.org/CVERecord?id=CVE-2026-67214 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=CVE-2026-69153 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-70907 https://www.cve.org/CVERecord?id=CVE-2026-70907 Référence CVE CVE-2026-71290 https://www.cve.org/CVERecord?id=CVE-2026-71290 Référence CVE CVE-2026-7168 https://www.cve.org/CVERecord?id=CVE-2026-7168 Référence CVE CVE-2026-71852 https://www.cve.org/CVERecord?id=CVE-2026-71852 Référence CVE CVE-2026-71870 https://www.cve.org/CVERecord?id=CVE-2026-71870 Référence CVE CVE-2026-72848 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-64958 Référence CVE CVE-2026-65432 https://www.cve.org/CVERecord?id=CVE-2026-65432 Référence CVE CVE-2026-66053 https://www.cve.org/CVERecord?id=CVE-2026-66053 Référence CVE CVE-2026-66142 https://www.cve.org/CVERecord?id=CVE-2026-66142 Référence CVE CVE-2026-66143 https://www.cve.org/CVERecord?id=CVE-2026-66143 Référence CVE CVE-2026-66144 https://www.cve.org/CVERecord?id=CVE-2026-66144 Référence CVE CVE-2026-66713 https://www.cve.org/CVERecord?id=CVE-2026-66713 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-73088 https://www.cve.org/CVERecord?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-75878 https://www.cve.org/CVERecord?id=CVE-2026-75878 Référence CVE CVE-2026-7884 https://www.cve.org/CVERecord?id=CVE-2026-7884 Référence CVE CVE-2026-8646 https://www.cve.org/CVERecord?id=CVE-2026-8646 Référence CVE CVE-2026-87958 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2026-6790 Référence CVE CVE-2026-68494 https://www.cve.org/CVERecord?id=CVE-2026-68494 Référence CVE CVE-2026-68525 https://www.cve.org/CVERecord?id=CVE-2026-68525 Référence CVE CVE-2026-68569 https://www.cve.org/CVERecord?id=CVE-2026-68569 Référence CVE CVE-2026-68763 https://www.cve.org/CVERecord?id=CVE-2026-68763 Référence CVE CVE-2026-68945 https://www.cve.org/CVERecord?id=CVE-2026-68945 Référence CVE CVE-2026-69151 https://www.cve.org/CVERecord?id=CVE-2026-69151 Référence CVE CVE-2026-69152 https://www.cve.org/CVERecord?id=CVE-2026-69152 Référence CVE CVE-2026-69153 https://www.cve.org/CVERecord?id=CVE-2026-69153 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-6938 https://www.cve.org/CVERecord?id=CVE-2026-6938 Référence CVE CVE-2026-70907 https://www.cve.org/CVERecord?id=CVE-2026-70907 Référence CVE CVE-2026-71290 https://www.cve.org/CVERecord?id=CVE-2026-71290 Référence CVE CVE-2026-71491 https://www.cve.org/CVERecord?id=CVE-2026-71491 Référence CVE CVE-2026-73088 https://www.cve.org/CVERecord?id=CVE-2026-73088 Référence CVE CVE-2026-73089 https://www.cve.org/CVERecord?id=CVE-2026-73089 Référence CVE CVE-2026-73180 https://www.cve.org/CVERecord?id=CVE-2026-73180 Référence CVE CVE-2026-75595 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1094Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2026-66053 Référence CVE CVE-2026-66142 https://www.cve.org/CVERecord?id=CVE-2026-66142 Référence CVE CVE-2026-66143 https://www.cve.org/CVERecord?id=CVE-2026-66143 Référence CVE CVE-2026-66144 https://www.cve.org/CVERecord?id=CVE-2026-66144 Référence CVE CVE-2026-66373 https://www.cve.org/CVERecord?id=CVE-2026-66373 Référence CVE CVE-2026-6733 https://www.cve.org/CVERecord?id=CVE-2026-6733 Référence CVE CVE-2026-6734 https://www.cve.org/CVERecord?id=CVE-2026-6734 Référence CVE CVE-2026-6790 https://www.cve.org/CVERecord?id=CVE-2026-6790 Référence CVE CVE-2026-6918 https://www.cve.org/CVERecord?id=CVE-2026-6918 Référence CVE CVE-2026-69247 https://www.cve.org/CVERecord?id=CVE-2026-69247 Référence CVE CVE-2026-69248 https://www.cve.org/CVERecord?id=CVE-2026-69248 Référence CVE CVE-2026-69249 https://www.cve.org/CVERecord?id=CVE-2026-69249 Référence CVE CVE-2026-7246 https://www.cve.org/CVERecord?id=CVE-2026-7246 Référence CVE CVE-2026-75838 https://www.cve.org/CVERecord?id=CVE-2026-75838 Référence CVE CVE-2026-8177 https://www.cve.org/CVERecord?id=CVE-2026-8177 Référence CVE CVE-2026-8400 https://www.cve.org/CVERecord?id=CVE-2026-8400 Référence CVE CVE-2026-8646 https://www.cve.org/CVERecord?id=CVE-2026-8646 Référence CVE CVE-2026-8723 https://www.cve.org/CVERecord?id=CVE-2026-

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
For more information visit https://access.redhat.com/errata/RHSA-2026:70965
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 3 Aug 2026 · Last source change 4 Aug 2026, 14:09 UTC · CWE-208 · Observable Timing Discrepancy

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-52446
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 44.0.0, < 50.0.0 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    After
    >= 44.0.0, < 50.0.0 · Fixed: For more information visit https://access.redhat.com/errata/RHSA-2026:70965
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-69247 to remediation: access.redhat.com/CVE-2026-69247.
    Before
    remediation: access.redhat.com/CVE-2026-69247
    After
    remediation: access.redhat.com/CVE-2026-69247
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 9; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9 · Fixed: python-cryptography-main@aarch64 as a component of Red Hat Hardened Images; python-cryptography-main@src as a component of Red Hat Hardened Images; python-cryptography-main@x86_64 as a component of Red Hat Hardened Images
    After
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 9; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9 · Fixed: registry.redhat.io/rhaii/vllm-cpu-rhel9@sha256:81c5994dc20321f8bd3969099eade78ef127cbd79f2d0ccea101c773e4c7fa4d_amd64 as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-cuda-rhel9@sha256:0d22e2301ce26ef68effda5d3a4a20381ad0ea34d1240e159e245bd44c2e125b_amd64 as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-cuda-rhel9@sha256:e491c3b169ec77c37dbe0eb9c2b35dd976ca6e968f43b5d72ad5c4095f48d2ed_arm64 as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-rocm-rhel9@sha256:1a30359d6ca5d0891e403b9b0a23c0ae1ad6e30a2429b9b42e246b874fe8859a_amd64 as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-spyre-rhel9@sha256:11ad6e13c41728944d933c7abe01d1d10ecb3f8e8b4f0da50ec53b7df6f036a8_amd64 as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-spyre-rhel9@sha256:340cecbac6b168cb0414f242832f153e6f3655052bfd98252f9e2d507509cabf_ppc64le as a component of Red Hat AI Inference Server 3.4; registry.redhat.io/rhaii/vllm-spyre-rhel9@sha256:40c5ed966b693ab9b6f1e71455c04eb42c5c0010c356ab5526218ab3034bede2_s390x as a component of Red Hat AI Inference Server 3.4; python-cryptography-0:50.0.0-1.hum1@src as a component of Red Hat Hardened Images; python3-cryptography-0:50.0.0-1.hum1@aarch64 as a component of Red Hat Hardened Images; python3-cryptography-0:50.0.0-1.hum1@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    >= 44.0.0, < 50.0.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    >= 44.0.0, < 50.0.0 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  6. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-69247 to remediation: access.redhat.com/CVE-2026-69247.
    Before
    remediation: access.redhat.com/CVE-2026-69247
    After
    remediation: access.redhat.com/CVE-2026-69247
    Red Hat Product Security ↗
  7. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  8. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 9; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9; python-cryptography.src as a component of Red Hat Hardened Images
    After
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 9; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9 · Fixed: python-cryptography-main@aarch64 as a component of Red Hat Hardened Images; python-cryptography-main@src as a component of Red Hat Hardened Images; python-cryptography-main@x86_64 as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  9. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9
    After
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography as a component of Red Hat Enterprise Linux 9; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9; python-cryptography.src as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  10. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10
    After
    python3-cryptography as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 10; python3.14-cryptography.src as a component of Red Hat Enterprise Linux 9
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-52446↗Red Hat Product Security security advisory↗CVE authority or vendor reference · GitHub GHSA-G6CJ-PR64-35W5↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-69247 · cve.blacktree.nl