CVE-2026-81019

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

Published Aug 28, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The flaw in wolfProvider causes the 8‑byte explicit AES‑GCM nonce to be generated once when the TLS write key is set and never incremented for subsequent records. This means every TLS 1.2 or DTLS 1.2 AES‑GCM packet within a session is encrypted with the same key‑nonce pair, violating GCM security requirements and exposing the keystream. An attacker who observes two ciphertexts from the same connection can recover the plaintexts and forge authentication tags, compromising confidentiality and integrity of all data transmitted in that session.

Affected Systems

wolfSSL Inc.'s wolfProvider library is affected. All releases earlier than version 1.2.2 exhibit the nonce‑reuse flaw for TLS 1.2 and DTLS 1.2 AES‑GCM traffic. Non‑TLS use of the cipher and the AES‑CCM mode are not impacted, and TLS 1.3 traffic is fully protected.

Risk and Exploitability

The CVSS score of 7.4 signals a moderate‑to‑high risk. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the attacker must have the ability to capture multiple records from a TLS session. The likely attack vector is passive network traffic observation; once two ciphertexts are available, the attacker can exploit the nonce reuse to recover plaintexts and forge authentication tags.

Remediation

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.


OpenCVE Recommended Actions

  • Upgrade wolfProvider to version 1.2.2 or later to ensure per‑record nonce incrementation
  • If an upgrade is not immediately feasible, configure the application to use AES‑CCM mode or TLS 1.3 instead of AES‑GCM with TLS 1.2/DTLS 1.2
  • Restrict or disable TLS 1.2/DTLS 1.2 AES‑GCM traffic in the deployment configuration, enforcing TLS 1.3 usage where possible

Generated by OpenCVE AI on August 28, 2026 at 17:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:wolfssl:wolfprovider:*:*:*:*:*:*:*:*
Type Values Removed Values Added
First Time appeared Wolfssl
Wolfssl wolfprovider
Vendors & Products Wolfssl
Wolfssl wolfprovider
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

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-323

    Reusing a Nonce, Key Pair in Encryption

Sources

Status
PUBLISHED
Assigner
wolfSSL
Published
Updated
Aug 28, 2026, 6:22 PM
Reserved
Aug 26, 2026, 2:40 PM
Status
Analyzed
Published
Aug 28, 2026, 4:18 PM
Modified
Sep 29, 2026, 7:11 PM