CVE-2026-75803: OpenSSL EVP_Cipher() AEAD Authentication Bypass with Empty Ciphertext
- Vendor
- OpenSSL Software Foundation
CVE-2026-75803 is an authentication-tag verification bypass in OpenSSL's EVP_Cipher() interface affecting ChaCha20-Poly1305 and AES-OCB decryption. When an empty ciphertext is processed and the operation is finalized through EVP_Cipher(), the function can return success without verifying the supplied AEAD authentication tag. Applications that interpret this return value as confirmation of message authenticity may consequently accept forged empty-ciphertext messages. The OpenSSL FIPS modules in branches 4.0, 3.6, 3.5, 3.4, and 3.0 are unaffected because they do not implement the affected algorithms.
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.
Successful exploitation compromises message integrity and authentication by allowing an application to accept an empty-ciphertext message whose authentication tag has not been validated. The resulting application-level consequences depend on the meaning and permitted effects of such messages. EDK II deployments using the affected embedded OpenSSL implementation may likewise accept forged messages. The cryptographic flaw alone does not establish arbitrary code execution or component takeover.
Mitigation
If you can’t patch tonight, do this now.
Where protocol-compatible, reject empty ciphertexts before invoking the affected decryption path. Otherwise, avoid relying on EVP_Cipher() success as proof of authentication for empty-ciphertext ChaCha20-Poly1305 or AES-OCB messages; use an API sequence that explicitly performs and confirms authentication-tag verification. Until patched, restrict access to application interfaces that accept attacker-controlled messages and invoke the vulnerable path.
Remediation
Patch, then assume compromise.
Install vendor-provided OpenSSL security updates, including updates for applications, firmware, appliances, and container images that bundle the library. Branch-specific security releases include OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, 1.1.1zi, and 1.0.2zr; confirm applicability for the deployed branch. Debian 12 provides a fix in 3.0.22-1~deb12u1. Ubuntu 24.04 LTS and 22.04 LTS provide fixes in 3.0.13-0ubuntu3.15 and 3.0.2-0ubuntu1.29, respectively. On Ubuntu 26.04 LTS, install openssl and libssl3t64 version 3.5.5-1ubuntu3.5 or later: USN-8678-3 corrects an incomplete earlier fix. Update affected EDK II firmware packages separately. Restart or redeploy dependent services, or reboot as required, to ensure patched components are loaded.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-75803 exploited in the wild?
- As of Nov 7, 2026, Mallory has no reports of CVE-2026-75803 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-75803?
- As of Nov 7, 2026, Mallory has found no public exploit for CVE-2026-75803.
- Is there a patch for CVE-2026-75803?
- Install vendor-provided OpenSSL security updates, including updates for applications, firmware, appliances, and container images that bundle the library. Branch-specific security releases include OpenSSL 4.0.2, 3.6.4, 3.5.8, 3.4.7, 3.0.22, 1.1.1zi, and 1.0.2zr; confirm applicability for the deployed branch.
- What products are affected by CVE-2026-75803?
- OpenSSL Software Foundation Openssl.
- How severe is CVE-2026-75803?
- CVE-2026-75803 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.25% (17th percentile) as of Nov 7, 2026.
Recent activity
42 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.