Read the docs

Out-of-Bounds Read and Incorrect IV Length Handling in AES-GCM-SIV

Priority LOW 38CWE-125Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-125 and the CVSS impact.

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. Setting an AES-GCM-SIV IV with a length other than 12 bytes through EVP_CipherInit_ex() can cause a heap out-of-bounds read (CWE-125) when the IV is too short, and a longer IV is silently truncated instead of rejected. An attacker who knows one message and its tag under one IV can forge a message and tag that verify under a different IV whose first bytes match, and an application passing a short IV may crash.

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

Description from the CNA

Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected. Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV. CWE: CWE-125: Out-of-bounds Read Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length. The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery. Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application. FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00211 11th 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 OpenSSL to 4.1.1, 4.0.4 or 3.5.10, depending on the release branch in use.

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-88051 AES-GCM-SIV AAD forgery in OpenSSL after empty AAD updatePriority 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-95692
  2. 2026-11-10 Alias added: GHSA-529p-7xq5-2rq6
  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