CVE-2026-75803
UNSCOREDDescription
Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3.1 Vector
No CVSS vector data available.
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-354 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-48795 | Medium | 5.9 | 93% | - | Fix |
| CVE-2019-1166 | Medium | 5.9 | 68% | - | - |
| CVE-2024-3596 | Critical | 9.0 | 15% | - | Fix |
| CVE-2020-26141 | Medium | 6.5 | 3.1% | - | Fix |
| CVE-2020-25862 | High | 7.5 | 2.4% | - | Fix |
| CVE-2020-8838 | Medium | 6.4 | 1.6% | - | - |
Common questions
How do I fix CVE-2026-75803?
Published advisories record a fix for 4 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-75803 being actively exploited?
Not that we know of. CVE-2026-75803 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
What does CVE-2026-75803 affect?
Published advisories record a fix for openssl (Debian), libssl3 (Ubuntu), libssl3t64 (Ubuntu), openssl (Ubuntu). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-75803
Markdown
[](https://tridentstack.com/cve/CVE-2026-75803)HTML
<a href="https://tridentstack.com/cve/CVE-2026-75803"><img src="https://tridentstack.com/cve/badge/CVE-2026-75803.svg" alt="CVE-2026-75803"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.