CVE-2026-88823: OpenSSL AES-GCM-SIV AAD Forgery After Zero-Length Incremental AAD Update
CVE-2026-88823 is an authentication weakness in OpenSSL's AES-GCM-SIV implementation. A zero-length Additional Authenticated Data (AAD) update incorrectly discards previously accumulated AAD instead of leaving it unchanged. Applications processing AAD incrementally with an empty fragment therefore generate or verify authentication tags that exclude all AAD preceding that fragment, allowing that data to be forged. A related context-reinitialization defect retains accumulated AAD from previous context usage and incorporates it into a new message. Affected release ranges 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 AES-GCM-SIV is implemented only in the default provider, outside the FIPS module boundary.
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.
The vulnerability compromises the integrity and authenticity of AAD supplied before an empty incremental update. An attacker can alter the excluded AAD without invalidating the authentication tag when verification follows the vulnerable processing pattern. Application-level consequences depend on how the unauthenticated data is used. Separately, retained AAD across context reinitialization causes authentication to incorporate data from previous context usage rather than only the intended current message.
Mitigation
If you can’t patch tonight, do this now.
No vendor-specified temporary workaround is identified.
Remediation
Patch, then assume compromise.
Apply the upstream OpenSSL fix or upgrade the applicable branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available. The fix makes zero-length AAD updates no-ops and clears accumulated AAD when a context is reinitialized with a key or nonce; parameter-only reinitialization preserves AAD. As of November 17, 2026, the fixes are committed to the public repository, with the corresponding releases scheduled for December 1, 2026. Packages without vendor fixes require migration to a maintained, corrected build.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-88823 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-88823 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-88823?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-88823.
- Is there a patch for CVE-2026-88823?
- Apply the upstream OpenSSL fix or upgrade the applicable branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available. The fix makes zero-length AAD updates no-ops and clears accumulated AAD when a context is reinitialized with a key or nonce; parameter-only reinitialization preserves AAD.
- How severe is CVE-2026-88823?
- CVE-2026-88823 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.14% (4th percentile) as of Nov 17, 2026.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.