Skip to main content
Mallory
MediumVulnerability

CVE-2026-88822: OpenSSL QUIC Uninitialized Stack Disclosure in Automated Peer Detection

Published Nov 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 9 in a dayToday
CVSS6.5Medium · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-88822CWE-457 · Use of Uninitialized Variable

CVE-2026-88822 is an uninitialized-variable vulnerability in OpenSSL QUIC automated peer-address detection. During the TLS handshake on an already connected socket, OpenSSL calls getpeername() with an address buffer large enough for supported address families but supplies an insufficient buffer-length argument for larger addresses such as IPv6. OpenSSL subsequently accepts the full address length returned by getpeername(), treating uninitialized stack bytes as valid portions of the peer address. Using this invalid address for outgoing packets can break connectivity and disclose stack data through packet destination addresses. Affected supported releases are OpenSSL 3.5.0 before 3.5.10, 4.0.0 before 4.0.4, and 4.1.0 before 4.1.1. OpenSSL FIPS modules are unaffected because they do not implement QUIC.

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.

Affected applications can lose QUIC connectivity when outgoing packets use an invalid destination address. Passive observers of outgoing network traffic may recover uninitialized process stack bytes incorporated into that address. The amount and sensitivity of disclosed data are not established. OpenSSL rates the vulnerability Low severity.

Mitigation

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

Where application configuration permits, avoid QUIC automated peer-address detection on already connected sockets until the OpenSSL fix is deployed.

Remediation

Patch, then assume compromise.

Apply the upstream correction available in the public OpenSSL repository, or upgrade the corresponding release branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available. As of November 11, 2026, the advisory schedules releases containing these fixes for December 1, 2026.

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.
FAQ

Frequently asked questions

Is CVE-2026-88822 exploited in the wild?
As of Nov 16, 2026, Mallory has no reports of CVE-2026-88822 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-88822?
As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-88822.
Is there a patch for CVE-2026-88822?
Apply the upstream correction available in the public OpenSSL repository, or upgrade the corresponding release branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available. As of November 11, 2026, the advisory schedules releases containing these fixes for December 1, 2026.
How severe is CVE-2026-88822?
CVE-2026-88822 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 0.19% (9th percentile) as of Nov 16, 2026.
Activity feed

Recent activity

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

View more in app →
ghsa syntheticNews · Nov 10, 2026GHSA-m2vh-6qf5-47p9An uninitialized-memory vulnerability in OpenSSL's QUIC automated peer detection during the SSL handshake on already connected sockets. An incorrectly sized buffer length passed to getpeername() prevents retrieval of larger addresses, such as IPv6 addresses. The returned full address length is nevertheless accepted, causing uninitialized stack data to be used as part of the outgoing destination address. This can break connectivity and disclose stack data to passive network observers. The advisory explicitly states that the FIPS modules in versions 4.0, 3.6, 3.5, 3.4, and 3.0 are unaffected because they do not implement the affected protocol.Read more ↗openssl libraryNews · Nov 10, 2026Vulnerabilities 4.1 | OpenSSL LibraryLow-severity uninitialized-memory flaw in OpenSSL QUIC automated peer detection on connected sockets. An incorrectly sized buffer length passed to getpeername() can leave larger peer addresses, such as IPv6 addresses, partially uninitialized. OpenSSL subsequently uses the returned address length and invalid address for outgoing packets, potentially breaking connectivity and exposing stack bytes to passive network observers. Affected versions are 4.1.0 before 4.1.1, 4.0.0 before 4.0.4, and 3.5.0 before 3.5.10. FIPS modules are unaffected because QUIC is outside their boundary.Read more ↗tenable nessus pluginsNews · Nov 10, 2026Linux Distros Unpatched Vulnerability : CVE-2026-88822 | Tenable®An uninitialized stack-data disclosure vulnerability in OpenSSL's QUIC automated peer detection. During the SSL handshake on an already connected socket, an incorrectly sized buffer length passed to getpeername() can cause an invalid peer address containing uninitialized stack data to be used for outgoing packets. This can break connectivity and expose stack data to passive network observers. The content identifies OpenSSL 3.5.0 onward as affected, with an upstream fix in 3.5.10, but states that the distribution packages covered by this plugin have no vendor-supplied patch or known solution. The listed FIPS modules are unaffected because they do not implement the affected protocol.Read more ↗tenable nessus pluginsNews · Nov 10, 2026OpenSSL 4.0.0 < 4.0.4 Multiple Vulnerabilities | Tenable®OpenSSL QUIC automated peer detection supplies an insufficient address-buffer length to getpeername(), then accepts the returned full address length. Larger addresses, such as IPv6 addresses, can consequently incorporate uninitialized stack data. Using the resulting invalid destination can disrupt connectivity and disclose stack data to passive network observers. FIPS modules are unaffected. The plugin recommends OpenSSL 4.0.4 or later and also identifies a fix in 3.5.10.Read more ↗
+4 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 activity1Community discussion across Reddit, Mastodon, and other social sources.