wolfSSL wolfEngine up to 1.4.0 AES-CCM key management

Summaryinfo

A vulnerability marked as critical has been reported in wolfSSL wolfEngine up to 1.4.0. This impacts an unknown function of the component AES-CCM. This manipulation causes key management. This vulnerability is tracked as CVE-2026-81341. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability classified as critical was found in wolfSSL wolfEngine up to 1.4.0. Affected by this vulnerability is an unknown code of the component AES-CCM. The manipulation with an unknown input leads to a key management vulnerability. The CWE definition for the vulnerability is CWE-320. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at wolfssl.com. This vulnerability is known as CVE-2026-81341 since 08/26/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 1.4.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• wolfSSL

Name

• wolfEngine

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4.0

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion