Skip to main content
Mallory
HighVulnerability

CVE-2026-18798: Double Free in OpenSSL QUIC Server INITIAL Packet Processing

Published Aug 25, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 5 in a dayToday
CVSS7.5High · v3.1
EPSS1.7%78th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
OpenSSL Software Foundation
IdentifiersCVE-2026-18798CWE-415 · Double Free

CVE-2026-18798 is a double-free vulnerability in OpenSSL's QUIC server implementation. The default packet handler, port_default_packet_handler(), creates a QUIC record-layer receive (QRX) object to validate an INITIAL packet, then passes it to port_bind_channel() during connection creation. If channel binding fails, port_bind_channel() frees the QRX object, and the packet handler's error path frees it again. A malformed INITIAL packet with a destination connection ID shorter than eight bytes triggers this failure when ossl_quic_lcidm_enrol_odcid() rejects the identifier length. The resulting heap corruption typically terminates the server process, causing denial of service. The OpenSSL FIPS module is unaffected because QUIC lies outside its boundary.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

An unauthenticated remote attacker can cause heap corruption and typically crash an affected QUIC server process, interrupting services provided by that process. No confidentiality or integrity impact has been established. Remote code execution has not been demonstrated and is considered highly improbable.

Mitigation

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

Until patched, restrict affected QUIC listeners to trusted networks or peers, or temporarily disable exposed QUIC services where operationally feasible. Protocol-aware filtering that rejects QUIC INITIAL packets with destination connection IDs shorter than eight bytes may reduce exposure but does not replace patching.

Remediation

Patch, then assume compromise.

Install the applicable vendor security update for OpenSSL and any products or container images bundling the affected library. Fixed upstream releases include OpenSSL 3.5.8, 3.6.4, and 4.0.2 for their respective branches; confirm applicability against the vendor's per-CVE guidance. Distribution fixes include Ubuntu 26.04 LTS package 3.5.5-1ubuntu3.4, Debian trixie package 3.5.7-1~deb13u2, RHEL 9 package 3.5.8-1.el9_8, and RHEL 10 package 3.5.8-1.el10_2. Use the corresponding security-fixed package or a later vendor-supported update. Restart or redeploy applications after updating so they load the corrected library.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
OpenSSL Software FoundationOpensslapplication
FAQ

Frequently asked questions

Is CVE-2026-18798 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-18798 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-18798?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-18798.
Is there a patch for CVE-2026-18798?
Install the applicable vendor security update for OpenSSL and any products or container images bundling the affected library. Fixed upstream releases include OpenSSL 3.5.8, 3.6.4, and 4.0.2 for their respective branches; confirm applicability against the vendor's per-CVE guidance.
What products are affected by CVE-2026-18798?
OpenSSL Software Foundation Openssl.
How severe is CVE-2026-18798?
CVE-2026-18798 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.7% (78th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

46 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+17 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity12Community discussion across Reddit, Mastodon, and other social sources.