CVE-2026-81341
MEDIUMDescription
wolfEngine before 1.4.1 sources the explicit AES-CCM nonce for TLS 1.2 and DTLS 1.2 records from the record input buffer instead of the TLS sequence number carried in the additional authenticated data. Because the record layer leaves the explicit-nonce field for the cipher to populate, the value read is constant across records, so every AES-CCM record within a connection is encrypted under an identical key and nonce pair. Reusing a CCM key and nonce weakens confidentiality (identical keystream across records, so a known record recovers the others) and integrity (authentication tag forgery). Only wolfEngine is affected; wolfProvider is not. AES-GCM under wolfEngine is tracked separately. AES-CCM cipher suites are not enabled by default and must be explicitly selected, which limits exposure. 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:L/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 10% 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-81341?
No published fix for CVE-2026-81341 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-81341 being actively exploited?
Not that we know of. CVE-2026-81341 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-81341?
CVE-2026-81341 has a CVSS v3 base score of 6.5, rated medium. 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-81341
Markdown
[](https://tridentstack.com/cve/CVE-2026-81341)HTML
<a href="https://tridentstack.com/cve/CVE-2026-81341"><img src="https://tridentstack.com/cve/badge/CVE-2026-81341.svg" alt="CVE-2026-81341"></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.