Quick answers
- Is CVE-2026-81019 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81019 being exploited in the wild.
- How severe is CVE-2026-81019?
- High severity, with a CVSS score of 7.4, published 28 August 2026.
- Which products and versions are affected?
- Wolfssl wolfProvider before 1.2.2.
- Is there a fix for CVE-2026-81019?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81019 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81019?
- Check whether you run Wolfssl wolfProvider at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
wolfProvider contains a cryptographic nonce generation flaw in AES-GCM mode for TLS 1.2 and DTLS 1.2. The 8-byte explicit nonce is generated once when the TLS write key is established and is never incremented for subsequent records, causing every encrypted record within a connection to use an identical key-nonce pair. Reusing GCM key-nonce pairs violates the cryptographic guarantee of authenticated encryption: XORing two ciphertexts encrypted under the same key and nonce recovers the XOR of their plaintexts (known-plaintext recovery), and the GHASH authentication key is leaked, enabling forgery of authentication tags. The vulnerability requires a network-reachable TLS/DTLS 1.2 connection with AES-GCM cipher negotiation. AES-CCM, TLS 1.3, and non-TLS uses of the cipher are unaffected. Fixed in wolfProvider 1.2.2.
Affected products
- wolfSSL wolfProvider before 1.2.2
Timeline
- 2026-08-28: disclosed