CVE-2026-95692: OpenSSL AES-GCM-SIV IV-Length Handling Out-of-Bounds Read and IV-Commitment Failure
CVE-2026-95692 is an incorrect initialization-vector length handling vulnerability in OpenSSL AES-GCM-SIV. During initialization through EVP_CipherInit_ex() or equivalent provider initialization, ossl_aes_gcm_siv_init() copies the expected 12-byte nonce length rather than respecting the caller-supplied buffer length. A shorter IV can therefore cause a heap out-of-bounds read, while an oversized IV is silently truncated instead of rejected. Truncation allows the same message and authentication tag to verify under distinct IVs sharing the same initial 12 bytes, constituting an IV-commitment failure rather than a classic existential forgery. Affected release ranges are OpenSSL 3.5.0 before 3.5.10, 4.0.0 before 4.0.4, and 4.1.0 before 4.1.1. OpenSSL FIPS modules are unaffected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Short IV buffers can cause a small heap out-of-bounds read and potentially crash the consuming application, resulting in denial of service. Oversized IVs lose their trailing bytes during cryptographic processing, breaking authentication-tag binding to the complete supplied IV. An observed message and tag can consequently be accepted under another IV with the same 12-byte prefix without changing the message. Practical severity is limited by the requirement for nonstandard application IV lengths and the small, length-controlled over-read. Arbitrary message forgery, exploitable memory disclosure, and code execution are not established.
Mitigation
If you can’t patch tonight, do this now.
Validate AES-GCM-SIV IV lengths before passing buffers to EVP_CipherInit_ex() or equivalent provider initialization. Require exactly 12 bytes and reject both shorter and longer IVs. Enforce this check at every application entry point accepting caller-supplied IVs.
Remediation
Patch, then assume compromise.
Apply the upstream fix merged into the public OpenSSL repository, or upgrade to the corrected release for the deployed branch: OpenSSL 3.5.10, 4.0.4, or 4.1.1, or a later corrected release. As of November 17, 2026, these releases are scheduled for December 1, 2026. Distribution-packaged installations require a vendor update or corresponding backport; availability varies by vendor.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-95692 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-95692 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-95692?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-95692.
- Is there a patch for CVE-2026-95692?
- Apply the upstream fix merged into the public OpenSSL repository, or upgrade to the corrected release for the deployed branch: OpenSSL 3.5.10, 4.0.4, or 4.1.1, or a later corrected release. As of November 17, 2026, these releases are scheduled for December 1, 2026.
- How severe is CVE-2026-95692?
- CVE-2026-95692 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.21% (11th percentile) as of Nov 17, 2026.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.