CVE-2026-6092
Received Received - Intake
Encrypt-then-MAC Bypass in wolfSSL

Publication date: 2026-06-25

Last updated on: 2026-06-25

Assigner: wolfSSL Inc.

Description
When HAVE_ENCRYPT_THEN_MAC is configured, the implementation could fall back to MAC-then-Encrypt rather than enforcing Encrypt-then-MAC.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-25
Last Modified
2026-06-25
Generated
2026-06-26
AI Q&A
2026-06-26
EPSS Evaluated
N/A
NVD
CVE-2026-6092
EUVD
EUVD-2026-39573
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-757 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.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability occurs when the HAVE_ENCRYPT_THEN_MAC configuration is enabled. Instead of enforcing the Encrypt-then-MAC approach, the implementation could incorrectly fall back to using MAC-then-Encrypt.

Impact Analysis

The fallback from Encrypt-then-MAC to MAC-then-Encrypt can weaken the security guarantees of the cryptographic process, potentially exposing encrypted data to certain types of cryptographic attacks that Encrypt-then-MAC is designed to prevent.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-6092. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart