CVE-2026-81019

wolfProvider before 1.2.2 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
Configurations

Configuration 1 (hide)

cpe:2.3:a:wolfssl:wolfprovider:*:*:*:*:*:*:*:*

History

29 Sep 2026, 19:11

Type Values Removed Values Added
References () https://www.wolfssl.com/docs/security-vulnerabilities/ - () https://www.wolfssl.com/docs/security-vulnerabilities/ - Vendor Advisory
CPE cpe:2.3:a:wolfssl:wolfprovider:*:*:*:*:*:*:*:*
First Time Wolfssl wolfprovider
Wolfssl

Information

Published : 2026-08-28 16:18

Updated : 2026-09-29 19:11


NVD link : CVE-2026-81019

Mitre link : CVE-2026-81019

CVE.ORG link : CVE-2026-81019


JSON object : View

Products Affected

wolfssl

  • wolfprovider
CWE
CWE-323

Reusing a Nonce, Key Pair in Encryption