Bug 2547741 - CVE-2026-69249 python-cryptography: python-cryptography: Duplicate self-signed intermediates can cause exponential path-building [fedora-all]
Summary: CVE-2026-69249 python-cryptography: python-cryptography: Duplicate self-signe...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python-cryptography
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Jeremy Cline
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["2a1b53ca-a14a-45d3-b13e-c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-07 22:50 UTC by Melissa Ing
Modified: 2026-10-07 22:50 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Melissa Ing 2026-10-07 22:50:40 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 49.0.0, when resolving invalid certificate chains that include duplicate copies of self-signed certificates, the processing recursively invokes the same candidate, leading to an exponential blowup. Although the limitation that the chain depth cannot exceed a specified maximum depth prevents unbounded recursion and guarantees termination, an attacker-controlled certificate chain can lead the processing to easily take more than 5s to reject in testing. This amplification could form the basis for a resource exhaustion denial of service attack. The core issue arises in the recursive nature of build_chain_inner, which does not de-duplicate against previously analyzed candidates. As the correctness of validation is not affected, the integrity of a system cannot be compromised through this vector, only its availability. This issue is fixed in 49.0.0.


Note You need to log in before you can comment on or make changes to this bug.