Threat Intelligence Database
Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threat Intelligence
Click on any threat for detailed analysis and mitigation recommendations
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. Join the discussion | CVE Database V5 | 08/03/2026, 21:26:45 UTC Added: 08/03/2026, 21:48:52 UTC |
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In versions 45.0.0 through 48.0.0, if an intermediate constrained CA permits the DNS name foo.example.com, and the leaf certificate has a wildcard in its DNS SAN of *.example.com, python-cryptography's verifier accepts which allows escaping outside of the permitted names. The core issue is in DNSConstraint::matches, where a wildcard pattern was treated as matching a more-specific permitted constraint even though *.example.com can expand to sibling names such as bar.example.com outside foo.example.com. This allows acceptance of an invalid certificate chain. This issue is fixed in 49.0.0. Join the discussion | CVE Database V5 | 08/03/2026, 21:21:43 UTC Added: 08/03/2026, 21:48:52 UTC |
A timing discrepancy vulnerability exists in the pyca cryptography package versions 44.0.0 up to but not including 50.0.0. The issue involves the pkcs7_decrypt_der, pkcs7_decrypt_pem, and pkcs7_decrypt_smime functions which leak information about the length of the decrypted RSA encryptedKey through observable timing differences and distinct error messages. This leakage can be exploited as a Bleichenbacher oracle against the content-encryption key if an application decrypts attacker-supplied EnvelopedData and reflects the outcome. The vulnerability is fixed in version 50.0.0. Join the discussion | CVE Database V5 | 08/03/2026, 21:16:32 UTC Added: 08/03/2026, 21:48:52 UTC |
0 cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. From 45.0.0 to before 46.0.7, if a non-contiguous buffer was passed to APIs which accepted Python buffers (e.g. Hash.update()), this could lead to buffer overflows. This vulnerability is fixed in 46.0.7. Join the discussion | CVE Database V5 | 04/08/2026, 20:49:41 UTC Added: 04/08/2026, 21:05:48 UTC |
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to version 46.0.6, DNS name constraints were only validated against SANs within child certificates, and not the "peer name" presented during each validation. Consequently, cryptography would allow a peer named bar.example.com to validate against a wildcard leaf certificate for *.example.com, even if the leaf's parent certificate (or upwards) contained an excluded subtree constraint for bar.example.com. This issue has been patched in version 46.0.6. Join the discussion | CVE Database V5 | 03/31/2026, 02:04:36 UTC Added: 03/31/2026, 14:23:24 UTC |
0 A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data. Join the discussion | CVE Database V5 | 02/05/2024, 20:45:49 UTC Added: 11/10/2025, 15:28:18 UTC |
cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Calling `load_pem_pkcs7_certificates` or `load_der_pkcs7_certificates` could lead to a NULL-pointer dereference and segfault. Exploitation of this vulnerability poses a serious risk of Denial of Service (DoS) for any application attempting to deserialize a PKCS7 blob/certificate. The consequences extend to potential disruptions in system availability and stability. This vulnerability has been patched in version 41.0.6. Join the discussion | CVE Database V5 | 11/29/2023, 18:50:24 UTC Added: 11/03/2025, 22:01:27 UTC |
0 cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. In affected versions `Cipher.update_into` would accept Python objects which implement the buffer protocol, but provide only immutable buffers. This would allow immutable objects (such as `bytes`) to be mutated, thus violating fundamental rules of Python and resulting in corrupted output. This now correctly raises an exception. This issue has been present since `update_into` was originally introduced in cryptography 1.8. Join the discussion | CVE Database V5 | 02/07/2023, 20:54:03 UTC Added: 11/03/2025, 22:01:15 UTC |
Showing 1 to 8 of 8 results