CVE-2026-81020

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce discloses the keystream (the XOR of two ciphertexts equals the XOR of their plaintexts, so one known record recovers the others) and leaks the GHASH authentication key, enabling authentication tag forgery. AES-CCM, TLS 1.3, and non-TLS use of the cipher are not affected.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/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 computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available.
generic Patch Available🟡 PoC Available

wolfSSL Security Vulnerabilities | Documentation - wolfSSL

https://www.wolfssl.com/docs/security-vulnerabilities/

Vendor Advisories for CVE-2026-81020(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 12× in last 7d / 12× 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.

  1. 2026-08-30 05:23 UTCEG score recompute
  2. 2026-08-30 05:23 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 18:26 UTCGHSA enrichment
  5. 2026-08-29 07:27 UTCGHSA enrichment
  6. 2026-08-28 20:28 UTCEG score recompute
  7. 2026-08-28 20:27 UTCGHSA enrichment
  8. 2026-08-28 19:44 UTCEG score recompute
  9. 2026-08-28 19:44 UTCGHSA enrichment
  10. 2026-08-28 16:31 UTCEG score recompute
  11. 2026-08-28 15:28 UTCEG score recompute
  12. 2026-08-28 15:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81020?
CVE-2026-81020 is a high vulnerability published on August 28, 2026. wolfEngine before 1.4.1 generates the 8-byte explicit AES-GCM nonce once when the TLS write key is set and never increments it per record. As a result every TLS 1.2 and DTLS 1.2 AES-GCM record within a connection is encrypted under an identical key and nonce pair. Reusing a GCM key and nonce…
When was CVE-2026-81020 disclosed?
CVE-2026-81020 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81020 actively exploited?
CVE-2026-81020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-81020?
CVE-2026-81020 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-81020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81020, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81020

Explore →

Is Your Infrastructure Affected by CVE-2026-81020?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs