CVE-2026-88823
Description
Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment. Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message. CWE: CWE-325: Missing Cryptographic Step Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message. The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD. FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary.
Weakness
- CWE-325: Missing Cryptographic Step
CISA SSVC decision points
| Exploitation | none |
|---|---|
| Automatable | yes |
| Technical impact | partial |
| Scored | 2026-11-16 |
Timeline
- 2026-11-10Published by the CNA18:15 UTC
- 2026-11-10Published in NVD19:21 UTC · 1 hour 5 minutes after the CNA
- 2026-11-16CISA SSVC decision recorded6 days after publication
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| openssl openssl | from 3.5.0 before 3.5.10fixed in 3.5.10from 4.0.0 before 4.0.4fixed in 4.0.4from 4.1.0 before 4.1.1fixed in 4.1.1 | 3.5.104.0.44.1.1 |
References
- https://github.com/openssl/openssl/commit/159e1de0c448d7b9f09ad768c8e141def4aa1eb4
- https://github.com/openssl/openssl/commit/2f5fc833ff9b5bfe00b32f8b5c74f73c5773c682
- https://github.com/openssl/openssl/commit/6747b1a278816dd7db46438040a70b0b5e5e0a90
- https://openssl-library.org/news/secadv/20261110.txt
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-88823'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-88823'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-88823'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-88823'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).