Read the docs

AES-GCM-SIV AAD forgery in OpenSSL after empty AAD update

Priority LOW 38CWE-325Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.

Summary

OpenSSL versions from 4.1.0 before 4.1.1, from 4.0.0 before 4.0.4, and from 3.5.0 before 3.5.10 are affected. The AES-GCM-SIV implementation treats a zero-length additional authenticated data (AAD) update as a reset that discards AAD supplied earlier, so messages authenticate without the earlier AAD (CWE-325). An attacker can forge the AAD of such a message, because the data the application meant to authenticate is left unauthenticated.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00142 3rd percentileScored 2026-11-16
Fix Fixed OpenSSL (OpenSSL): 4.1.1, 4.0.4, 3.5.10

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
OpenSSLOpenSSL4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.104.1.1, 4.0.4, 3.5.10Patch availableCNA
  • OpenSSL VendorOpenSSL Affected 4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10 Fixed in 4.1.1, 4.0.4, 3.5.10 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*——OpenSSL
  • cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* Versions — — ·OpenSSL

Remediation

Upgrade to OpenSSL 4.1.1, 4.0.4 or 3.5.10. The sources list no advisory identifiers for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

  • Fix · CNA OpenSSL (OpenSSL) Fixed in 4.1.1, 4.0.4, 3.5.10

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    OpenSSL — openssl-library.org/news/secadv/20261110.txt

    5 records Highest priority Priority LOW 5 LOW

    Other records, highest priority first

    • TI-2026-88358 Infinite loop in OpenSSL CMS_encrypt() with an EC group order of 1Priority LOW 38
    • TI-2026-88065 Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIVPriority LOW 38
    • TI-2026-88064 Use-after-free in OpenSSL QUIC client via retransmitted CRYPTO framesPriority LOW 34

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-88823
  2. 2026-11-10 Alias added: GHSA-mwpv-32cf-mj9v
  3. 2026-11-16 CVSS score added · CISA ADP
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2022-01915 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2021-02645 SM2 Decryption Buffer Overflow CVSS 3.1CRITICAL 9.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
  • TI-2022-01176 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2014-00154 Out-of-bounds read in OpenSSL TLS and DTLS Heartbeat handling KEVCVSS 3.1HIGH 7.5
  • TI-2025-14107 Stack buffer overflow in CMS (Auth)EnvelopedData parsing CVSS 3.1HIGH 8.8
See all 328 →

Sources