Skip to main content
Mallory
Unrated

Unbounded Memory Growth in the OpenSSL QUIC PATH_CHALLENGE Handler

IdentifiersCVE-2026-34183CWE-770

CVE-2026-34183 is a denial-of-service vulnerability in the integrated OpenSSL QUIC stack. A malicious remote QUIC peer can flood a client or server with packets containing PATH_CHALLENGE frames. For each received PATH_CHALLENGE, the local QUIC implementation allocates a corresponding PATH_RESPONSE frame. That allocation is only released after the peer acknowledges receipt of the PATH_RESPONSE. A malicious peer can intentionally avoid acknowledging those responses, causing unbounded heap growth over time. The issue affects OpenSSL QUIC client and server operation and is described as an unbounded allocation flaw in PATH_CHALLENGE handling.

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 allows a remote peer to exhaust heap memory in an application using the vulnerable OpenSSL QUIC stack as either a client or server. This can lead to abnormal process termination and denial of service. The primary impact described in the available material is resource exhaustion rather than code execution or data exposure.

Mitigation

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

No specific workaround is provided in the supplied content. Practical mitigation is to avoid exposing vulnerable OpenSSL QUIC endpoints to untrusted peers until patched, or disable/use alternatives to the affected QUIC functionality where operationally feasible. Vendor advisories cited in the content indicate no workaround is available in some distributions.

Remediation

Patch, then assume compromise.

Upgrade OpenSSL to a fixed release. The provided content indicates fixes are available in OpenSSL 4.0.1, 3.6.3, 3.5.7, and 3.4.6; affected versions include 4.0.0 before 4.0.1, 3.6.0 before 3.6.3, 3.5.0 before 3.5.7, and 3.4.0 before 3.4.6. Downstream vendors may also provide patched package versions. The OpenSSL FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected because the QUIC stack is outside the FIPS module boundary.
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.