CVE-2026-88822: OpenSSL QUIC Uninitialized Stack Disclosure in Automated Peer Detection
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
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.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.