CVE-2026-75803
Publication date 25 August 2026
Last updated 2 September 2026
Ubuntu priority
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.
Read the notes from the security team
Why is this CVE low priority?
OpenSSL developers have rated this low severity
Status
| Package | Ubuntu Release | Status |
|---|---|---|
| openssl | 26.04 LTS resolute |
Fixed 3.5.5-1ubuntu3.5
|
| 24.04 LTS noble |
Fixed 3.0.13-0ubuntu3.15
|
|
| 22.04 LTS jammy |
Fixed 3.0.2-0ubuntu1.29
|
|
| 20.04 LTS focal |
Not affected
|
|
| 18.04 LTS bionic |
Not affected
|
|
| 16.04 LTS xenial |
Not affected
|
|
| 14.04 LTS trusty |
Not affected
|
|
| openssl-fips | 26.04 LTS resolute | Not in release |
| 24.04 LTS noble |
Fixed 3.0.13-0ubuntu3.15+Fips1
|
|
| 22.04 LTS jammy | Not in release | |
| openssl1.0 | 26.04 LTS resolute | Not in release |
| 24.04 LTS noble | Not in release | |
| 22.04 LTS jammy | Not in release | |
| 18.04 LTS bionic |
Not affected
|
|
| nodejs | 26.04 LTS resolute |
Not affected
|
| 24.04 LTS noble |
Not affected
|
|
| 22.04 LTS jammy |
Not affected
|
|
| 20.04 LTS focal |
Not affected
|
|
| 18.04 LTS bionic |
Needs evaluation
|
|
| 16.04 LTS xenial |
Needs evaluation
|
|
| 14.04 LTS trusty |
Not affected
|
|
| edk2 | 26.04 LTS resolute |
Needs evaluation
|
| 24.04 LTS noble |
Needs evaluation
|
|
| 22.04 LTS jammy |
Not affected
|
|
| 20.04 LTS focal |
Not affected
|
|
| 18.04 LTS bionic |
Not affected
|
|
| 16.04 LTS xenial |
Not affected
|
|
| edk2-hwe | 26.04 LTS resolute |
Needs evaluation
|
| 24.04 LTS noble | Not in release | |
| 22.04 LTS jammy | Not in release |
Notes
mdeslaur
edk2 in jammy embeds OpenSSL 1.1.1j edk2 in noble embeds OpenSSL 3.0.9 edk2 in plucky embeds OpenSSL 3.4.0 edk2 in questing embeds OpenSSL 3.4.0 edk2 in resolute embeds OpenSSL 3.5.1 edk2 in stonking embeds OpenSSL 3.5.1 nodejs in jammy embeds OpenSSL 1.1.1m 4.0, 3.6, 3.5, 3.4, and 3.0 are vulnerable While USN-8678-1 mentions that this CVE was fixes in Ubuntu 26.04 LTS, it was unfortunately not. A subsequent USN will fix this in 26.04 LTS.
Patch details
| Package | Patch details |
|---|---|
| openssl |
References
Related Ubuntu Security Notices (USN)
- USN-8678-1
- OpenSSL vulnerabilities
- 25 August 2026
- USN-8678-3
- OpenSSL vulnerability
- 31 August 2026