Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-95692

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

No exploitation reported by the sources we read.

  • Published2026-11-10
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-11-1018:16CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As openssl, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • OpenSSLother versions: not affected
    Affected
    • ≥ 4.1.0, < 4.1.1fixed in 4.1.1semver
    • ≥ 4.0.0, < 4.0.4fixed in 4.0.4semver
    • ≥ 3.5.0, < 3.5.10fixed in 3.5.10semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • edk2Ubuntu:Pro:20.04:LTSall versions · no fixed version listedand 1 other package
  • edk2Ubuntu:Pro:18.04:LTSall versions · no fixed version listedand 3 other packages
  • edk2Ubuntu:Pro:16.04:LTSall versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:26.10all versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:26.04:LTSall versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:24.04:LTSall versions · no fixed version listedand 1 other package
  • edk2Ubuntu:22.04:LTSall versions · no fixed version listedand 1 other package
  • nodejsUbuntu:Pro:22.04:LTSall versions · no fixed version listed

20 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2026-11-10
Last Modified
2026-11-16
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-529p-7xq5-2rq6

Frequently asked questions

What is CVE-2026-95692?

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.

Is CVE-2026-95692 actively exploited?

Active exploitation of CVE-2026-95692 has not been confirmed. Its EPSS score was 0.2% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-95692?

CVE-2026-95692 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record