All reports
Low

openssl: OpenSSL: Message authentication bypass via zero-length AAD update

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-88823

Probability of exploitation in the next 30 days: 0.27%

FIRST EPSS · 2026-11-21

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.

A flaw was found in OpenSSL. This vulnerability allows an attacker to bypass message authentication when an application processes data using the AES-GCM-SIV cipher. The cipher implementation improperly treats an empty Additional Authenticated Data (AAD) chunk—contextual data verified alongside encrypted messages—as a reset, excluding previously supplied data from the calculated authentication tag. As a result, data intended to be protected is silently left unverified, enabling an attacker to forge or tamper with the message without detection.