CVE-2026-81020

published 28 Aug 2026 · updated 28 Aug 2026

wolfEngine reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record

7.4HighCVSS 7.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
wolfSSL<=1.4.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-81020 severity on Zeptric[![CVE-2026-81020](https://zeptric.io/badge/cve/CVE-2026-81020.svg)](https://zeptric.io/cve/CVE-2026-81020)