---
id: CVE-2026-81341
title: >-
  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
summary: >-
  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…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N'
cwe:
  - CWE-323
vendor: wolfssl
product: wolfengine
affected:
  - wolfengine < 1.4.1
patched:
  - wolfengine 1.4.1
published: '2026-08-28'
updated: '2026-09-29'
sourceUpdated: '2026-09-29T19:10:08.287'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-81341'
references:
  - url: 'https://www.wolfssl.com/docs/security-vulnerabilities/'
    label: facts@wolfssl.com
tags:
  - nvd
epss: 0.00318
epssPercentile: 0.22289
ingestedAt: '2026-09-29T19:44:04.119Z'
---

## Overview

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

- `wolfengine < 1.4.1`

## Remediation

Upgrade past the affected range:

- `wolfengine 1.4.1`