CVE-2026-81019: wolfProvider reuses the AES-GCM nonce on every TLS 1.2 / DTLS 1.2 record
wolfSSL Inc. · wolfProvider
Fixed in 1.2.2 · Affected: wolfSSL Inc. wolfProvider before 1.2.2 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 32% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- wolfSSL Inc. · wolfProviderVersions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- wolfSSL Inc.
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-81019 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.