Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-42764Published 2026-06-09

CVE-2026-42764 — OpenSSL

high

As of 2026-06-10, CVE-2026-42764 is a HIGH-severity vulnerability in OpenSSL, CVSS v3.1 7.5, EPSS 0.7% (54.5th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-42764, most recently “HollowByte: OpenSSL Pre-Authentication TLS DoS Flaw Bloats Server Memory With 11-Byte Payload”.

CVSS v3.1
7.5/10High
EPSS
0.7%Higher than 54.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
1Campaigns referencing it
Priority
5.9/10Threadlinqs triage score
Published
Updated 2026-06-10
CVSS v3.1 7.5 (HIGH) · EPSS 0.7% (higher than 54.5% of all scored CVEs) · Priority 5.9/10 · Published 2026-06-09

Last updated:

What is CVE-2026-42764?

Issue summary: Receiving a QUIC initial packet with an invalid token may trigger a NULL pointer dereference in the OpenSSL QUIC server with address validation disabled. Impact summary: NULL pointer dereference typically causes abnormal termination of the affected QUIC server process and a Denial of Service. If the address validation is disabled in the OpenSSL QUIC server implementation, an attacker can crash the server by sending an initial packet with an invalid or expired token. By default, the client address validation is enabled in the OpenSSL QUIC server implementation, which makes the default configuration not vulnerable to this issue. However if the SSL_LISTENER_FLAG_NO_VALIDATE is used with the SSL_new_listener() call, the address validation is disabled making the vulnerable code reachable. The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

The record classifies CVE-2026-42764 under weakness class CWE-476. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 140 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (FIRST)
0.7% probability of exploitation in the next 30 days, higher than 54.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
5.9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-06-09, last modified 2026-06-10

Is CVE-2026-42764 being exploited?

It currently carries a trending score of 19 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-42764

No vendor patch reference has been recorded for CVE-2026-42764 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-42764

1 tracked threat in the Threadlinqs corpus references CVE-2026-42764, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .

Vendor advisory and patch