CVE-2026-88823
AES-GCM-SIV AAD Forgery After Zero-length Incremental AAD Update
No exploitation reported by the sources we read.
- Published2026-11-10
- WeaknessCWE-325
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-1018:15CVE publishedCNA
Versions per branch
Products declared by the CNA1 product
As openssl, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- OpenSSLother versions: not affectedAffected
- ≥ 4.1.0, < 4.1.1fixed in 4.1.1semver
- ≥ 4.0.0, < 4.0.4fixed in 4.0.4semver
- ≥ 3.5.0, < 3.5.10fixed in 3.5.10semver
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-10
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Packages
- edk2Ubuntu:Pro:20.04:LTSall versions · no fixed version listedand 1 other package
- edk2Ubuntu:Pro:18.04:LTSall versions · no fixed version listedand 3 other packages
- edk2Ubuntu:Pro:16.04:LTSall versions · no fixed version listedand 2 other packages
- edk2Ubuntu:26.10all versions · no fixed version listedand 2 other packages
- edk2Ubuntu:26.04:LTSall versions · no fixed version listedand 2 other packages
- edk2Ubuntu:24.04:LTSall versions · no fixed version listedand 1 other package
- edk2Ubuntu:22.04:LTSall versions · no fixed version listedand 1 other package
- nodejsUbuntu:Pro:22.04:LTSall versions · no fixed version listed
20 more package ranges on OSV.dev
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- PoC-in-GitHubno public repository identifiedread 2026-11-16
- Metasploit modules
- none listed Metasploit Framework
Sources
- NVDCVE recordread 2026-11-16
- CISA-ADPSSVC decisionnone2026-11-16
- CISA-ADPCVSS 3.17.52026-11-16
- CNAweakness (CWE)CWE-3252026-11-10
- FIRST EPSSEPSS score0.1 %2026-11-15
- OSVaffected packages—
- GitHub Advisoriesadvisory—
Identifiers
- AZL-113960same flawAzure Linux · MIT
- AZL-114004same flawAzure Linux · MIT
- AZL-114019same flawAzure Linux · MIT
- AZL-114028same flawAzure Linux · MIT
- AZL-114067same flawAzure Linux · MIT
- AZL-114079same flawAzure Linux · MIT
- EUVD-2026-121609same flawENISA EUVD · LicenseRef-ENISA-legal-notice
- GHSA-mwpv-32cf-mj9vsame flawGitHub Advisory Database · CC-BY-4.0
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- Published
- 2026-11-10
- Last Modified
- 2026-11-16
- NVD status
- Awaiting Analysis
- GitHub Advisory
- GHSA-mwpv-32cf-mj9v
Frequently asked questions
What is CVE-2026-88823?
Is CVE-2026-88823 actively exploited?
What is the CVSS score for CVE-2026-88823?
Running OpenSSL? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- GitHub Advisory Database · CC-BY-4.0 · GHSA-mwpv-32cf-mj9v
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- OpenCVE · OpenCVE terms of service · terms restrict redistribution
- OSV.dev · Per record, as its publisher states it: each row carries the label in sourceLicense when one is served
- CISA Vulnrichment · CC0-1.0