PoC Monitor
← All CVEs
CVE-2026-81020published 28 Aug 2026 14:42 UTCData: JSON · API

wolfSSL Inc. wolfEngine

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.4high · scored by CNA · CWE-323
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

wolfSSL Inc. wolfEngine
  • <= 1.4.0

Mitigation

Upgrade to wolfEngine 1.4.1, which increments the explicit nonce after each record. As an interim mitigation use AES-CCM or TLS 1.3 instead of TLS 1.2 / DTLS 1.2 AES-GCM.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published28 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.