Skip to main content
Mallory
HighVulnerability

CVE-2026-88823: OpenSSL AES-GCM-SIV AAD Forgery After Zero-Length Incremental AAD Update

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
CVSS7.5High · v3.1
EPSS0.14%4th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-88823CWE-325 · Missing Cryptographic Step

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.

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.

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.

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-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.
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-mwpv-32cf-mj9vAn OpenSSL AES-GCM-SIV flaw causes zero-length AAD updates to discard previously supplied AAD, leaving that data unauthenticated and allowing attackers to forge it. Context re-initialisation also incorrectly retains AAD from previous use. The described fix makes empty AAD updates a no-op and clears accumulated AAD when re-initialising with a key or nonce. OpenSSL FIPS modules are unaffected because AES-GCM-SIV is implemented only in the default provider.Read more ↗openssl libraryNews · Nov 10, 2026Vulnerabilities 4.1 | OpenSSL LibraryLow-severity authentication flaw in OpenSSL AES-GCM-SIV. When an application supplies fragmented AAD containing an empty fragment, earlier fragments are silently excluded from authentication, allowing an attacker to forge that AAD. Context reinitialization also incorrectly retains previously accumulated AAD. 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. Fixes make empty AAD updates no-ops and clear accumulated AAD when reinitializing with a key or nonce. FIPS modules are unaffected.Read more ↗tenable nessus pluginsNews · Nov 10, 2026Linux Distros Unpatched Vulnerability : CVE-2026-88823 | Tenable®An OpenSSL AES-GCM-SIV authentication flaw causes an empty AAD fragment to discard previously supplied AAD, allowing attackers to forge data that an application intended to authenticate. Context reinitialization can also incorrectly retain AAD from a previous message. The issue affects OpenSSL starting with 3.5.0 and is fixed upstream in 3.5.10. OpenSSL FIPS modules are unaffected. The Nessus advisory nevertheless identifies affected distribution packages as lacking a vendor-supplied patch and lists no known solution for those packages. The advisory assigns a CVSS v3 base score of 9.8.Read more ↗tenable nessus pluginsNews · Nov 10, 2026OpenSSL 4.0.0 < 4.0.4 Multiple Vulnerabilities | Tenable®OpenSSL AES-GCM-SIV incorrectly discards previously accumulated AAD when an application submits an empty AAD fragment, leaving earlier fragments unauthenticated and permitting their forgery. Context reinitialization also incorrectly retains AAD from the previous message. The fix makes empty updates a no-op and clears accumulated AAD when reinitializing with a key or nonce. 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.