CVE-2026-95692: OpenSSL AES-GCM-SIV heap out-of-bounds read in EVP_CipherInit_ex

CVE-2026-95692 · Severity: info · Published 2026-11-10

OpenSSL's AES-GCM-SIV cipher implementation contains a flaw in its IV (initialization vector) handling that can crash applications or allow attackers to forge encrypted messages. An application that passes an incorrectly-sized IV to the encryption function may read beyond its allocated memory, and improper truncation of longer IVs breaks the cryptographic binding between the IV and the authentication tag, allowing an attacker to swap IVs for previously-observed messages.

Technologies: OpenSSL. Vendors: OpenSSL.

Quick answers

Is CVE-2026-95692 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-95692 being exploited in the wild.
How severe is CVE-2026-95692?
Informational severity, published 10 November 2026.
Which products and versions are affected?
OpenSSL OpenSSL.
Is there a fix for CVE-2026-95692?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-95692 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-95692?
Check whether you run OpenSSL. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The AES-GCM-SIV implementation in OpenSSL's EVP_CipherInit_ex() copies a caller-supplied IV using the expected nonce size rather than the actual provided length, causing a heap out-of-bounds read when the IV is shorter than 12 bytes, and silently truncating longer IVs instead of rejecting them. This breaks IV commitment, allowing an attacker who observes a message-tag pair under one IV to forge a valid tag for the same message under a different IV with matching prefix bytes. The vulnerability requires non-standard IV lengths to trigger; standard 12-byte IVs are unaffected.

Affected products

  • OpenSSL OpenSSL

Timeline

  • 2026-11-10: disclosed

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.