wolfSSL E2M enforcement flaw: falls back to MAC-then-Encrypt
CVE-2026-6092 Published on June 25, 2026

Encrypt-then-MAC could fall back to MAC-then-Encrypt when HAVE_ENCRYPT_THEN_MAC is configured
When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall back to MAC-then-Encrypt rather than enforcing Encrypt-then-MAC.

NVD

Vulnerability Analysis

Attack Vector:
ADJACENT
Attack Complexity:
HIGH
Privileges Required:
LOW
User Interaction:
NONE

Weakness Type

What is an Algorithm Downgrade Vulnerability?

A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties. When a security mechanism can be forced to downgrade to use a less secure algorithm, this can make it easier for attackers to compromise the software by exploiting weaker algorithm. The victim might not be aware that the less secure algorithm is being used. For example, if an attacker can force a communications channel to use cleartext instead of strongly-encrypted data, then the attacker could read the channel by sniffing, instead of going through extra effort of trying to decrypt the data using brute force techniques.

CVE-2026-6092 has been classified to as an Algorithm Downgrade vulnerability or weakness.


Products Associated with CVE-2026-6092

Want to know whenever a new CVE is published for Wolfssl? stack.watch will email you.

Wolfssl
 

Affected Versions

wolfSSL: