CVE-2026-95692 openssl openssl: Out-of-bounds Read
openssl openssl: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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.
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 11th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-125 Out-of-bounds Read
- Published
- Modified
- Assigned by
- openssl (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-95692 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95692?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95692?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95692 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| OpenSSL | from 4.1.0 before 4.1.1 |
| OpenSSL | from 4.0.0 before 4.0.4 |
| OpenSSL | from 3.5.0 before 3.5.10 |
Fix and patched versions
- Alpaquita, BellSoft Hardened Containers: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | openssl | no fix listed | DEBIAN-CVE-2026-95692 |
| Ubuntu | 22.04:LTS, 24.04:LTS, Pro:20.04:LTS | edk2, openssl | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | 26.04:LTS, 26.10 | edk2, openssl, edk2-hwe | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:14.04:LTS, Pro:FIPS-updates:16.04:LTS, Pro:FIPS-updates:18.04:LTS and 4 more | openssl | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:16.04:LTS | edk2, nodejs, openssl | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:18.04:LTS | edk2, nodejs, openssl and 1 more | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:22.04:LTS | nodejs | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:22.04:LTS | openssl, openssl-fips | no fix listed | UBUNTU-CVE-2026-95692 |
| Ubuntu | Pro:FIPS-updates:24.04:LTS | openssl-fips | no fix listed | UBUNTU-CVE-2026-95692 |
| Alpaquita | 25, stream | openssl | 3.5.9-r1 | BELL-CVE-2026-95692 |
| BellSoft Hardened Containers | 25, stream | openssl | 3.5.9-r1 | BELL-CVE-2026-95692 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita · BellSoft Hardened Containers.
Attack patterns (CAPEC)
- CAPEC-540 Overread Buffers Likelihood: Low · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.