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.
CVE-2026-81341
Score 6.5 from GitHub Security Advisory published 2026-08-28. a secondary CVSS source baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026wolfSSL Security Vulnerabilities | Documentation - wolfSSL
https://www.wolfssl.com/docs/security-vulnerabilities/Vendor Advisories for CVE-2026-81341(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:32 UTCGHSA enrichment
- 2026-08-28 20:28 UTCEG score recompute
- 2026-08-28 20:27 UTCGHSA enrichment
- 2026-08-28 19:44 UTCEG score recompute
- 2026-08-28 19:44 UTCGHSA enrichment
- 2026-08-28 16:31 UTCEG score recompute
- 2026-08-28 15:28 UTCEG score recompute
- 2026-08-28 15:25 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-81341?
When was CVE-2026-81341 disclosed?
Is CVE-2026-81341 actively exploited?
What is the CVSS score of CVE-2026-81341?
How do I remediate CVE-2026-81341?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-81341
Is Your Infrastructure Affected by CVE-2026-81341?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.