Skip to main content
Mallory
High

NULL Pointer Dereference in OpenSSL QUIC Server Initial Packet Handling

IdentifiersCVE-2026-42764CWE-476· NULL Pointer Dereference

CVE-2026-42764 is a NULL pointer dereference vulnerability in the OpenSSL QUIC server implementation. The issue is triggered when the server receives a QUIC Initial packet containing an invalid or expired token while client address validation has been disabled. The vulnerable code path is reachable when applications create a listener with SSL_new_listener() using SSL_LISTENER_FLAG_NO_VALIDATE, which disables the default client address validation behavior. In that configuration, malformed token handling during QUIC initial packet processing can dereference a NULL pointer and terminate the server process. The issue affects OpenSSL 4.0.0 before 4.0.1, 3.6.0 before 3.6.3, and 3.5.0 before 3.5.7. The affected code is outside the OpenSSL FIPS module boundary, and the FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation causes abnormal termination of the affected OpenSSL QUIC server process, resulting in denial of service. Based on the provided information, the impact is limited to process crash/availability loss; no evidence is provided for code execution, memory disclosure, or privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

Keep client address validation enabled in the OpenSSL QUIC server implementation. Avoid using SSL_LISTENER_FLAG_NO_VALIDATE with SSL_new_listener(), since that non-default configuration disables address validation and makes the vulnerable code path reachable. Where immediate patching is not possible, review QUIC listener configuration and remove any explicit disabling of address validation.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release: 4.0.1 or later, 3.6.3 or later, or 3.5.7 or later, as appropriate for the deployed branch. Downstream consumers should also apply vendor-packaged updates where applicable. If running on an operating system distribution that ships OpenSSL, install the vendor security update for the affected package.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.