What’s Vulnerable › Vulnerabilities
CVE-2026-81341: wolfEngine reuses the AES-CCM nonce on TLS 1.2 / DTLS 1.2 records
- Severity: medium (CVSS 6.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-08-28 · updated 2026-09-29
- Weakness: CWE-323
Description
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.
Affected products
- wolfSSL Wolfengine: before 1.4.1 — fixed in 1.4.1
How to fix
Upgrade to a fixed version: wolfSSL Wolfengine 1.4.1. Check the vendor advisory for mitigations.
References
Get alerted when CVE-2026-81341 or the next vulnerability affects your stack