Low [CVE-2026-75803] AEAD forgeries possible with empty ciphertext in EVP_Cipher
This low-severity Red Hat Linux advisory covers CVE-2026-75803 affecting Red Hat Hardened Images, Confidential Cluster Operator, Confidential Compute Attestation.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
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. This allows remote attackers to submit forged messages that affected applications incorrectly accept as valid.
Red Hat rates this as Low since exploitation requires a rare API misuse pattern using EVP_Cipher() with empty ChaCha20-Poly1305 or AES-OCB ciphertexts.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
- chunkah-main-0.6.0-3.hum1
- python-cryptography-main-50.0.0-1.hum1
- openssl3-main-3.5.8-0.1.hum1
- openssl-main-3.5.8-0.1.hum1
- ruby3-3-main-3.3.10-23.6.hum1
- ruby4-0-main-4.0.6-37.3.hum1
- RHSA-2026:42825
- RHSA-2026:55543
- RHSA-2026:59635
- RHSA-2026:59641
- RHSA-2026:62562
- RHSA-2026:62563
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Mitigation checklist
- To mitigate this ensure that all integrity check values present in messages are properly checked in accordance with the protocol specification before they are parsed and used. Applications must rigorously calculate the checksum and explicitly verify that the received integrity value matches the calculated one to prevent malicious data injection.
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.