python-cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 42.0.0 through 48.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.
Weakness
The product does not properly control the allocation and maintenance of a limited resource.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | python3.14-cryptography-0:45.0.4-4.el10_2.5 | * |
| Red Hat Enterprise Linux 10 | RedHat | python-cryptography-0:43.0.0-4.el10_2.5 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | python-cryptography-0:43.0.0-4.el10_0.1 | * |
| Red Hat Enterprise Linux 9 | RedHat | python3.14-cryptography-0:45.0.4-4.el9_8.6 | * |
| Red Hat AI Inference Server 3.4 | RedHat | rhaii/vllm-cpu-rhel9:1790075793 | * |
| Red Hat AI Inference Server 3.4 | RedHat | rhaii/vllm-spyre-rhel9:1790076141 | * |
| Red Hat AI Inference Server 3.4 | RedHat | rhaii/vllm-cuda-rhel9:1790090131 | * |
| Red Hat AI Inference Server 3.4 | RedHat | rhaii/vllm-rocm-rhel9:1790109620 | * |
| Red Hat Hardened Images | RedHat | python-cryptography-main-50.0.0-1.hum1 | * |
| Python-cryptography | Ubuntu | resolute | * |
| Python-cryptography | Ubuntu | upstream | * |
Potential Mitigations
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/147.html
- https://cwe.mitre.org/data/definitions/227.html
- https://cwe.mitre.org/data/definitions/492.html
References
- https://github.com/pyca/cryptography/commit/3763aa79b
- https://github.com/pyca/cryptography/commit/4a12cf49675a184e47f912b00b04f3a629283582
- https://github.com/pyca/cryptography/pull/14960
- https://github.com/pyca/cryptography/security/advisories/GHSA-jwv3-5hgf-82ww
- https://github.com/pypa/advisory-database/tree/main/vulns/cryptography/PYSEC-2026-3553.yaml
- https://github.com/pyca/cryptography/security/advisories/GHSA-jwv3-5hgf-82ww