| CVE-2026-97031 |
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted…
|
7.5
High
|
Oct 8, 2026 |
| CVE-2026-56862 |
Handshake messages, such as KeyUpdate, are always considered as state-advancing, regardless of whether a handshake has…
|
7.5
High
|
Aug 13, 2026 |
| CVE-2026-42505 |
Handshakes which used Encrypted Client Hello could be de-anonymized by a passive network observer due to a disclosure of…
|
5.3
Medium
|
Jul 8, 2026 |
| CVE-2026-32283 |
If one side of the TLS connection sends multiple key update messages post-handshake in a single record, the connection…
|
7.5
High
|
Apr 8, 2026 |
| CVE-2025-68121 |
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…
|
9.1
Critical
|
Feb 5, 2026 |
| CVE-2025-61730 |
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for…
|
5.3
Medium
|
Jan 28, 2026 |
| CVE-2025-58189 |
When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols…
|
5.3
Medium
|
Oct 29, 2025 |
| CVE-2023-45287 |
Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time
|
Not rated
|
Dec 5, 2023 |
| CVE-2023-39322 |
QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing…
|
Not rated
|
Sep 8, 2023 |
| CVE-2023-39321 |
Processing an incomplete post-handshake message for a QUIC connection can cause a panic
|
Not rated
|
Sep 8, 2023 |
| CVE-2023-29409 |
Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying…
|
Not rated
|
Aug 2, 2023 |
| CVE-2022-41724 |
Large handshake records may cause panics in crypto/tls
|
Not rated
|
Feb 28, 2023 |
| CVE-2022-30629 |
Non-random values for ticket_age_add in session tickets in crypto/tls before Go 1.17.11 and Go 1.18.3 allow an…
|
3.1
Low
|
Aug 9, 2022 |