Quick answers
- Is CVE-2026-81341 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81341 being exploited in the wild.
- How severe is CVE-2026-81341?
- Medium severity, with a CVSS score of 6.5, published 28 August 2026.
- Which products and versions are affected?
- Wolfssl wolfEngine before 1.4.1.
- Is there a fix for CVE-2026-81341?
- 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-81341 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81341?
- Check whether you run Wolfssl wolfEngine 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
wolfEngine sources the explicit AES-CCM nonce from the record input buffer instead of deriving it from the TLS sequence number in the additional authenticated data (AAD). Because the record layer leaves the explicit-nonce field for the cipher to populate, the value read is constant across records, resulting in key-nonce pair reuse. Reusing a CCM key and nonce produces identical keystreams across records, so an attacker who knows the plaintext of one record can recover the plaintext of others. Additionally, nonce reuse breaks CCM's authentication tag integrity, enabling authentication tag forgery. The vulnerability affects only wolfEngine (not wolfProvider), only explicit AES-CCM cipher suites (not AES-GCM), and only TLS 1.2 and DTLS 1.2 (not TLS 1.3 or non-TLS uses). Since AES-CCM suites are not enabled by default, exposure is limited to users who explicitly configure them.
Affected products
- wolfSSL wolfEngine before 1.4.1
Timeline
- 2026-08-28: disclosed