Skip to main content
No exploitation reportedAwaiting NVD analysis

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?

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
  1. 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 affected
    Affected
    • ≥ 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

Full record on NVD

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
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

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?

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.

Is CVE-2026-88823 actively exploited?

Active exploitation of CVE-2026-88823 has not been confirmed. Its EPSS score was 0.1% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-88823?

CVE-2026-88823 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

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

Sources for this record