TLS record disclosure and forgery via nonce reuse
Published Aug 28, 2026 · Updated Aug 28, 2026
Cryptographic nonce reuse in wolfSSL wolfEngine 0.9.0 through 1.4.0 allows man-in-the-middle attackers to recover and forge TLS records. Its AES-CCM TLS record path reads the explicit nonce from an unpopulated record-buffer field instead of copying the changing sequence number from the additional authenticated data. Exposure requires an explicitly selected AES-CCM suite under TLS 1.2 or DTLS 1.2; TLS 1.3, non-TLS cipher use, and wolfProvider are unaffected.
Summary
What happened
Cryptographic nonce reuse in wolfSSL wolfEngine 0.9.0 through 1.4.0 allows man-in-the-middle attackers to recover and forge TLS records. Its AES-CCM TLS record path reads the explicit nonce from an unpopulated record-buffer field instead of copying the changing sequence number from the additional authenticated data. Exposure requires an explicitly selected AES-CCM suite under TLS 1.2 or DTLS 1.2; TLS 1.3, non-TLS cipher use, and wolfProvider are unaffected.
The record
- CVE
- CVE-2026-81341
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- wolfSSL
- Product
- wolfEngine
- Classifications
- CWE-323, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo