Vulnerabilities
Recent vulnerabilities
Recent vulnerabilities from
π GNA-1 (CIRCL)
Select from 82 available sources using the dropdown above.
| ID | Description | Published | Updated |
|---|---|---|---|
| msrc_cve-2026-80255 | secure cookie attribute bypass with tab | 2026-09-08T01:04:43.000Z | 2026-09-09T01:58:23.000Z |
| msrc_cve-2026-80229 | OpenSSL provider use-after-free | 2026-09-08T01:04:30.000Z | 2026-09-09T01:58:09.000Z |
| msrc_cve-2026-13608 | OpenLDAP SASL authentication bypass | 2026-09-08T01:03:10.000Z | 2026-09-09T01:57:56.000Z |
| msrc_cve-2026-18924 | HTTP/2 server push UAF | 2026-09-08T01:03:36.000Z | 2026-09-09T01:57:40.000Z |
| msrc_cve-2026-19931 | Negotiate ambient user conn reuse | 2026-09-08T01:01:57.000Z | 2026-09-09T01:57:22.000Z |
| msrc_cve-2026-80230 | OpenSSL pinning bypass | 2026-09-08T01:04:17.000Z | 2026-09-09T01:56:58.000Z |
| msrc_cve-2026-56852 | Infinite loop on invalid input in golang.org/x/text | 2026-07-25T01:04:17.000Z | 2026-09-09T01:56:48.000Z |
| msrc_cve-2026-82209 | domain-scoped PSL domain cookie | 2026-09-08T01:03:58.000Z | 2026-09-09T01:56:38.000Z |
| msrc_cve-2020-29511 | The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications. | 2021-12-16T00:00:00.000Z | 2026-09-09T01:56:34.000Z |
| msrc_cve-2023-49292 | Possible private key restoration in go package github.com/ecies/go | 2025-09-04T04:54:22.000Z | 2026-09-09T01:56:29.000Z |
| msrc_cve-2020-29509 | The encoding/xml package in Go (all versions) does not correctly preserve the semantics of attribute namespace prefixes during tokenization round-trips which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications. | 2021-12-16T00:00:00.000Z | 2026-09-09T01:56:23.000Z |
| msrc_cve-2026-80231 | native CA store conn reuse | 2026-09-08T01:02:37.000Z | 2026-09-09T01:56:20.000Z |
| msrc_cve-2024-28960 | An issue was discovered in Mbed TLS 2.18.0 through 2.28.x before 2.28.8 and 3.x before 3.6.0 and Mbed Crypto. The PSA Crypto API mishandles shared memory. | 2024-11-28T00:00:00.000Z | 2026-09-09T01:56:11.000Z |
| msrc_cve-2025-48965 | Mbed TLS before 3.6.4 has a NULL pointer dereference because mbedtls_asn1_store_named_data can trigger conflicting data with val.p of NULL but val.len greater than zero. | 2026-09-03T01:08:27.000Z | 2026-09-09T01:56:05.000Z |
| msrc_cve-2025-52497 | Mbed TLS before 3.6.4 has a PEM parsing one-byte heap-based buffer underflow, in mbedtls_pem_read_buffer and two mbedtls_pk_parse functions, via untrusted PEM input. | 2026-09-03T01:08:18.000Z | 2026-09-09T01:55:59.000Z |
| msrc_cve-2026-82208 | wolfSSL CA-cache hit overrides callback | 2026-09-08T01:02:15.000Z | 2026-09-09T01:55:54.000Z |
| msrc_cve-2023-43615 | Mbed TLS 2.x before 2.28.5 and 3.x before 3.5.0 has a Buffer Overflow. | 2024-11-28T00:00:00.000Z | 2026-09-09T01:55:53.000Z |
| msrc_cve-2024-23744 | An issue was discovered in Mbed TLS 3.5.1. There is persistent handshake denial if a client sends a TLS 1.3 ClientHello without extensions. | 2024-11-28T00:00:00.000Z | 2026-09-09T01:55:47.000Z |
| msrc_cve-2025-66442 | In Mbed TLS through 4.0.0, there is a compiler-induced timing side channel (in RSA and CBC/ECB decryption) that only occurs with LLVM's select-optimize feature. TF-PSA-Crypto through 1.0.0 is also affected. | 2026-05-07T01:13:04.000Z | 2026-09-09T01:55:41.000Z |
| msrc_cve-2026-85393 | node-forge through 1.4.0 RSA PKCS#1 v1.5 Signature Forgery via Nested DigestAlgorithm Padding | 2026-09-07T01:02:18.000Z | 2026-09-09T01:55:38.000Z |
| msrc_cve-2026-25834 | Mbed TLS v3.3.0 up to 3.6.5 and 4.0.0 allows Algorithm Downgrade. | 2026-05-07T01:13:26.000Z | 2026-09-09T01:55:35.000Z |
| msrc_cve-2026-25835 | Mbed TLS before 3.6.6 and TF-PSA-Crypto before 1.1.0 misuse seeds in a Pseudo-Random Number Generator (PRNG). | 2026-05-07T01:12:58.000Z | 2026-09-09T01:55:29.000Z |
| msrc_cve-2026-34876 | An issue was discovered in Mbed TLS 3.x before 3.6.6. An out-of-bounds read vulnerability in mbedtls_ccm_finish() in library/ccm.c allows attackers to obtain adjacent CCM context data via invocation of the multipart CCM API with an oversized tag_len parameter. This is caused by missing validation of the tag_len parameter against the size of the internal 16-byte authentication buffer. The issue affects the public multipart CCM API in Mbed TLS 3.x, where mbedtls_ccm_finish() can be invoked directly by applications. In Mbed TLS 4.x versions prior to the fix, the same missing validation exists in the internal implementation; however, the function is not exposed as part of the public API. Exploitation requires application-level invocation of the multipart CCM API. | 2026-05-07T01:12:52.000Z | 2026-09-09T01:55:23.000Z |
| msrc_cve-2025-49600 | In MbedTLS 3.3.0 before 3.6.4, mbedtls_lms_verify may accept invalid signatures if hash computation fails and internal errors go unchecked, enabling LMS (Leighton-Micali Signature) forgery in a fault scenario. Specifically, unchecked return values in mbedtls_lms_verify allow an attacker (who can induce a hardware hash accelerator fault) to bypass LMS signature verification by reusing stale stack data, resulting in acceptance of an invalid signature. In mbedtls_lms_verify, the return values of the internal Merkle tree functions create_merkle_leaf_value and create_merkle_internal_value are not checked. These functions return an integer that indicates whether the call succeeded or not. If a failure occurs, the output buffer (Tc_candidate_root_node) may remain uninitialized, and the result of the signature verification is unpredictable. When the software implementation of SHA-256 is used, these functions will not fail. However, with hardware-accelerated hashing, an attacker could use fault | 2026-09-03T01:07:01.000Z | 2026-09-09T01:55:11.000Z |
| msrc_cve-2024-45159 | An issue was discovered in Mbed TLS 3.x before 3.6.1. With TLS 1.3, when a server enables optional authentication of the client, if the client-provided certificate does not have appropriate values in if keyUsage or extKeyUsage extensions, then the return value of mbedtls_ssl_get_verify_result() would incorrectly have the MBEDTLS_X509_BADCERT_KEY_USAGE and MBEDTLS_X509_BADCERT_KEY_USAGE bits clear. As a result, an attacker that had a certificate valid for uses other than TLS client authentication would nonetheless be able to use it for TLS client authentication. Only TLS 1.3 servers were affected, and only with optional authentication (with required authentication, the handshake would be aborted with a fatal alert). | 2024-11-28T00:00:00.000Z | 2026-09-09T01:55:05.000Z |
| msrc_cve-2026-86139 | In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow. | 2026-09-06T04:36:41.000Z | 2026-09-09T01:55:04.000Z |
| msrc_cve-2026-86141 | xmlregexp in libxml2 before 2.15.4 has a NULL pointer dereference in xmlRegNewParserCtxt after a strdup failure, i.e., it does not calculate a string length after NULL checking. | 2026-09-06T04:36:24.000Z | 2026-09-09T01:54:59.000Z |
| msrc_cve-2025-47917 | Mbed TLS before 3.6.4 allows a use-after-free in certain situations of applications that are developed in accordance with the documentation. The function mbedtls_x509_string_to_names() takes a head argument that is documented as an output argument. The documentation does not suggest that the function will free that pointer; however, the function does call mbedtls_asn1_free_named_data_list() on that argument, which performs a deep free(). As a result, application code that uses this function (relying only on documented behavior) is likely to still hold pointers to the memory blocks that were freed, resulting in a high risk of use-after-free or double-free. In particular, the two sample programs x509/cert_write and x509/cert_req are affected (use-after-free if the san string contains more than one DN). | 2026-09-03T01:06:42.000Z | 2026-09-09T01:54:59.000Z |
| msrc_cve-2026-84303 | gRPC-Go: xDS RBAC HTTP Filter bypass via mixed-case Header Matching and gRFC A41 validation evasion | 2026-09-07T01:59:28.000Z | 2026-09-09T01:54:53.000Z |
| msrc_cve-2026-80798 | nfc: llcp: reject PDUs shorter than the LLCP header | 2026-09-07T01:58:47.000Z | 2026-09-09T01:54:43.000Z |