RHSA-2026:71658HighCVSS 7.5

Red Hat Security Advisory: python-cryptography security update

Published
September 24, 2026
Last Modified
October 8, 2026

🔗 CVE IDs covered (1)

CVE-2026-69249 →

📋 Description

CVE-2026-69249 — python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building

🎯 Affected products14

  • Red Hat Enterprise Linux BaseOS (v. 10)
  • python-cryptography-0:43.0.0-4.el10_2.5.src as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python-cryptography-debugsource-0:43.0.0-4.el10_2.5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python-cryptography-debugsource-0:43.0.0-4.el10_2.5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python-cryptography-debugsource-0:43.0.0-4.el10_2.5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python-cryptography-debugsource-0:43.0.0-4.el10_2.5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-0:43.0.0-4.el10_2.5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-0:43.0.0-4.el10_2.5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-0:43.0.0-4.el10_2.5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-0:43.0.0-4.el10_2.5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-debuginfo-0:43.0.0-4.el10_2.5.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-debuginfo-0:43.0.0-4.el10_2.5.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-debuginfo-0:43.0.0-4.el10_2.5.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 10)
  • python3-cryptography-debuginfo-0:43.0.0-4.el10_2.5.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 10)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available.

🔗 References (4)