CVE-2026-95692
Description
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.
Weakness
- CWE-125: Out-of-bounds Read
CISA SSVC decision points
| Exploitation | none |
|---|---|
| Automatable | yes |
| Technical impact | partial |
| Scored | 2026-11-16 |
Timeline
- 2026-11-10Published by the CNA18:16 UTC
- 2026-11-10Published in NVD19:21 UTC · 1 hour 5 minutes after the CNA
- 2026-11-16CISA SSVC decision recorded6 days after publication
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| openssl openssl | from 3.5.0 before 3.5.10fixed in 3.5.10from 4.0.0 before 4.0.4fixed in 4.0.4from 4.1.0 before 4.1.1fixed in 4.1.1 | 3.5.104.0.44.1.1 |
References
- https://github.com/openssl/openssl/commit/257a3427aa0ef8d9dd2ef5b3e2d1c021a221b116
- https://github.com/openssl/openssl/commit/510872388f5d145cf870868b3d288a23822cb776
- https://github.com/openssl/openssl/commit/70a47ac78b6f3be1b22fb1551bd0bfcff4f29613
- https://openssl-library.org/news/secadv/20261110.txt
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-95692'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-95692'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-95692'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-95692'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).