CVE-2026-81019
wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record
- State
- Published
- Severity
- 7.4 High
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Reserved
- Aug 26, 2026
Description
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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 3.1 | 7.4 High | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N | wolfSSL |
Weaknesses
- CWE-323 Reusing a Nonce, Key Pair in Encryption
Affected Products
| Product | Versions |
|---|---|
wolfProviderwolfSSL Inc. |
|
References
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.