wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce discloses the keystream (the XOR of two ciphertexts equals the XOR of their plaintexts, so one known record recovers the others) and leaks the GHASH authentication key, enabling authentication tag forgery. AES-CCM, TLS 1.3, and non-TLS use of the cipher are not affected.
References
| Link | Resource |
|---|---|
| https://www.wolfssl.com/docs/security-vulnerabilities/ | Vendor Advisory |
Configurations
History
29 Sep 2026, 19:10
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Wolfssl
Wolfssl wolfengine |
|
| CPE | cpe:2.3:a:wolfssl:wolfengine:*:*:*:*:*:*:*:* | |
| References | () https://www.wolfssl.com/docs/security-vulnerabilities/ - Vendor Advisory |
Information
Published : 2026-08-28 16:18
Updated : 2026-09-29 19:10
NVD link : CVE-2026-81020
Mitre link : CVE-2026-81020
CVE.ORG link : CVE-2026-81020
JSON object : View
Products Affected
wolfssl
- wolfengine
CWE
CWE-323
Reusing a Nonce, Key Pair in Encryption
