CVE-2026-81019
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 15% of all known CVEs.
References
Related Vulnerabilities
Other CWE-323 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-49952 | Critical | 9.1 | 4.7% | - | - |
| CVE-2017-13082 | High | 8.1 | 3.8% | - | Fix |
| CVE-2017-13079 | Medium | 5.3 | 2.3% | - | Fix |
| CVE-2017-13078 | Medium | 5.3 | 2.3% | - | Fix |
| CVE-2017-13081 | Medium | 5.3 | 2.2% | - | Fix |
| CVE-2017-13080 | Medium | 5.3 | 2.2% | - | Fix |
Common questions
How do I fix CVE-2026-81019?
No published fix for CVE-2026-81019 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-81019 being actively exploited?
Not that we know of. CVE-2026-81019 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.24% is the estimated probability that it will be exploited in the next 30 days. That is higher than 15% of all scored CVEs.
How severe is CVE-2026-81019?
CVE-2026-81019 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-81019
Markdown
[](https://tridentstack.com/cve/CVE-2026-81019)HTML
<a href="https://tridentstack.com/cve/CVE-2026-81019"><img src="https://tridentstack.com/cve/badge/CVE-2026-81019.svg" alt="CVE-2026-81019"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.