Skip to main content
Mallory
HighVulnerability

CVE-2026-95692: OpenSSL AES-GCM-SIV IV-Length Handling Out-of-Bounds Read and IV-Commitment Failure

Published Nov 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 9 in a dayToday
CVSS7.5High · v3.1
EPSS0.21%11th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-95692CWE-125 · Out-of-bounds Read

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
ghsa syntheticNews · Nov 10, 2026GHSA-529p-7xq5-2rq6Incorrect IV-length handling in the AES-GCM-SIV implementation affects applications supplying IVs other than the standard 12 bytes through EVP_CipherInit_ex() or equivalent provider initialization. Short IVs can cause a heap out-of-bounds read and application crashes. Longer IVs are silently truncated, allowing an observed message and tag to verify under a different IV with matching initial bytes. This is an IV-commitment failure, not a classic existential forgery. Severity is limited by the small out-of-bounds read and the requirement for unusual application IV lengths. FIPS modules are unaffected.Read more ↗openssl libraryNews · Nov 10, 2026Vulnerabilities 4.1 | OpenSSL LibraryLow-severity IV-length validation flaw in OpenSSL AES-GCM-SIV. Applications supplying IVs shorter than the standard 12 bytes through EVP_CipherInit_ex() or equivalent provider initialization can trigger a small heap out-of-bounds read and potentially crash. Longer IVs are silently truncated, allowing an observed message and tag to verify under a different IV sharing the same initial bytes. This is an IV-commitment failure, not a classic existential forgery, and requires nonstandard IV lengths. Affected versions are 4.1.0 before 4.1.1, 4.0.0 before 4.0.4, and 3.5.0 before 3.5.10. FIPS modules are unaffected.Read more ↗tenable nessus pluginsNews · Nov 10, 2026Linux Distros Unpatched Vulnerability : CVE-2026-95692 | Tenable®An OpenSSL AES-GCM-SIV initialization flaw affects applications supplying IVs other than the standard 12-byte length. Short IVs can cause a heap out-of-bounds read and application crashes. Long IVs are silently truncated, allowing an observed message and authentication tag to verify under a different IV with the same prefix, breaking IV commitment. OpenSSL FIPS modules are unaffected. The plugin assigns a critical CVSS v3 score of 9.8, although its technical description notes limiting exploitation conditions. An upstream fix exists in OpenSSL 3.5.10, but the plugin reports no vendor-supplied patch or known solution for the distribution packages it detects.Read more ↗tenable nessus pluginsNews · Nov 10, 2026OpenSSL 4.0.0 < 4.0.4 Multiple Vulnerabilities | Tenable®OpenSSL AES-GCM-SIV initialization incorrectly handles IV lengths other than the standard 12 bytes. Short IVs can cause an out-of-bounds read or crash, while longer IVs are truncated, allowing an observed message and tag to verify under a different IV sharing the same initial bytes. This is an IV-commitment failure rather than a classic message forgery. Only applications supplying nonstandard IV lengths are affected; FIPS modules are unaffected. The plugin recommends OpenSSL 4.0.4 or later and also identifies a fix in 3.5.10.Read more ↗
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.