Metrics
Affected Vendors & Products
No advisories yet.
Solution
Upgrade to wolfEngine 1.4.1, which sources the explicit AES-CCM nonce from the TLS sequence number. As an interim mitigation do not enable AES-CCM cipher suites, or use TLS 1.3.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://www.wolfssl.com/docs/security-vulnerabilities/ |
|
Fri, 28 Aug 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | wolfEngine reuses the AES-CCM nonce on TLS 1.2 / DTLS 1.2 records | |
| Weaknesses | CWE-323 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: wolfSSL
Published:
Updated: 2026-08-28T14:43:43.099Z
Reserved: 2026-08-26T18:08:35.979Z
Link: CVE-2026-81341
No data.
Status : Received
Published: 2026-08-28T16:18:29.483
Modified: 2026-08-28T16:18:29.483
Link: CVE-2026-81341
No data.
OpenCVE Enrichment
Updated: 2026-08-28T16:45:03Z