CVE-2026-75803
Last modified
CVE-2026-75803 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.0.0, < 3.0.22 |
| Openssl | Openssl | >= 3.4.0, < 3.4.7 |
| Openssl | Openssl | >= 3.5.0, < 3.5.8 |
| Openssl | Openssl | >= 3.6.0, < 3.6.4 |
| Openssl | Openssl | >= 4.0.0, < 4.0.2 |
References
- https://openssl-library.org/news/secadv/20260825.txtVendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-75803?
How severe is CVE-2026-75803?
How do I fix CVE-2026-75803?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-75796The AI Engine WordPress plugin before 3.6.1 does not verify…7.2
- CVE-2026-75797The AI Engine WordPress plugin before 3.7.2 does not confin…7.7
- CVE-2026-75798The AI Engine WordPress plugin before 3.7.2 does not perfor…5.3
- CVE-2026-7580A vulnerability was detected in Exiftool up to 13.53. Impact…5.3
- CVE-2026-75800The Frontegg SAML SSO WordPress plugin through 1.0.1 does no…9.8
- CVE-2026-75802AjaxEditableChoiceLabel in wicket-extensions, when construct…5.4
- CVE-2026-75807The SAML Single Sign On – SSO Login plugin for WordPress is …7.5
- CVE-2026-75808Allocation of Resources Without Limits or Throttling in ASUS…5.7
- CVE-2026-75809Exposed IOCTL with insufficient access control in ASUS Armou…5.9
- CVE-2026-7581A security vulnerability has been detected in alexta69 MeTub…4.3
- CVE-2026-75810Exposed Dangerous Method or Function in ASUS Armoury Crate a…5.7
- CVE-2026-75811Improper Restriction of Software Interfaces to Hardware Feat…5.8
Are you affected by CVE-2026-75803?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
