Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Solution
Upgrade to wolfProvider 1.2.2, 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.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://www.wolfssl.com/docs/security-vulnerabilities/ |
|
Fri, 28 Aug 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wolfssl
Wolfssl wolfprovider |
|
| Vendors & Products |
Wolfssl
Wolfssl wolfprovider |
Fri, 28 Aug 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record | |
| Weaknesses | CWE-323 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: wolfSSL
Published:
Updated: 2026-08-28T18:22:34.803Z
Reserved: 2026-08-26T14:40:10.441Z
Link: CVE-2026-81019
No data.
Status : Received
Published: 2026-08-28T16:18:28.757
Modified: 2026-08-28T20:20:08.670
Link: CVE-2026-81019
No data.
OpenCVE Enrichment
Updated: 2026-08-28T20:31:49Z