CVE-2026-6726

HIGHPre-NVD 7.97.9
EchelonGraph scoreHIGH confidence

Score 7.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.9EG
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.9Exploit: None knownExposed: 0

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

An information leakage vulnerability was reported in the TCG TPM 2.0 reference code that could allow a local attacker with elevated privileges to obtain a credential from a TPM-aware CA for a falsified TPM key (such as an Attestation Key, DevID Key or TLS authentication key) and falsify other TPM 2.0 attestations with this key. See also TCG VRT0010.

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

Published

August 11, 2026

Last Modified

August 12, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 42× in last 7d / 52× 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-19 17:04 UTCEPSS rescore
  2. 2026-08-19 16:27 UTCVendor advisory
  3. 2026-08-19 16:27 UTCGHSA enrichment
  4. 2026-08-19 03:50 UTCVendor advisory
  5. 2026-08-19 03:50 UTCGHSA enrichment
  6. 2026-08-18 15:16 UTCEG score recompute
  7. 2026-08-18 15:16 UTCVendor advisory
  8. 2026-08-18 15:16 UTCGHSA enrichment
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 02:07 UTCEG score recompute
  12. 2026-08-18 02:07 UTCVendor advisory
  13. 2026-08-18 02:07 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 13:31 UTCVendor advisory
  16. 2026-08-17 13:31 UTCGHSA enrichment
  17. 2026-08-17 00:57 UTCEG score recompute
  18. 2026-08-17 00:57 UTCVendor advisory
  19. 2026-08-17 00:57 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 12:23 UTCEG score recompute
  23. 2026-08-16 12:23 UTCVendor advisory
  24. 2026-08-16 12:23 UTCGHSA enrichment
  25. 2026-08-16 02:15 UTCEPSS rescore
Show 27 more
  1. 2026-08-15 23:49 UTCVendor advisory
  2. 2026-08-15 23:49 UTCGHSA enrichment
  3. 2026-08-15 11:14 UTCEG score recompute
  4. 2026-08-15 11:14 UTCVendor advisory
  5. 2026-08-15 11:14 UTCGHSA enrichment
  6. 2026-08-15 01:31 UTCEPSS rescore
  7. 2026-08-14 22:39 UTCVendor advisory
  8. 2026-08-14 22:39 UTCGHSA enrichment
  9. 2026-08-14 10:05 UTCEG score recompute
  10. 2026-08-14 10:05 UTCVendor advisory
  11. 2026-08-14 10:05 UTCGHSA enrichment
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 21:30 UTCVendor advisory
  14. 2026-08-13 21:30 UTCGHSA enrichment
  15. 2026-08-13 08:55 UTCEG score recompute
  16. 2026-08-13 08:55 UTCVendor advisory
  17. 2026-08-13 08:55 UTCGHSA enrichment
  18. 2026-08-12 20:21 UTCVendor advisory
  19. 2026-08-12 20:21 UTCGHSA enrichment
  20. 2026-08-12 19:46 UTCEG score recompute 7.90
  21. 2026-08-12 19:46 UTCVendor advisory
  22. 2026-08-12 19:46 UTCGHSA enrichment
  23. 2026-08-12 19:45 UTCMITRE cvelistV5CVSS v3 → 7.9 · severity → HIGH
  24. 2026-08-12 13:51 UTCEPSS rescore
  25. 2026-08-11 16:35 UTCNVD update
  26. 2026-08-11 15:41 UTCEG score recompute
  27. 2026-08-11 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6726?
CVE-2026-6726 is a high vulnerability published on August 11, 2026. An information leakage vulnerability was reported in the TCG TPM 2.0 reference code that could allow a local attacker with elevated privileges to obtain a credential from a TPM-aware CA for a falsified TPM key (such as an Attestation Key, DevID Key or TLS authentication key) and falsify other TPM…
When was CVE-2026-6726 disclosed?
CVE-2026-6726 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6726 actively exploited?
CVE-2026-6726 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 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-6726?
CVE-2026-6726 has a CVSS v3.1 base score of 7.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-6726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6726, 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-6726

Explore →

Is Your Infrastructure Affected by CVE-2026-6726?

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