CVE-2026-6727

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

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

A timing side-channel vulnerability exists in the RSA OAEP decryption implementation. A privileged local attacker with access to the TPM command interface may be able to exploit timing differences to recover information that could allow decryption of ciphertexts encrypted to TPM-managed RSA keys, including the RSA Endorsement Key (EK), including import blobs, credential blobs, and session salts. Under certain conditions, this may also enable the forgery of TPM 2.0 attestations. Refer to TCGVRT0011.

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

Published

August 11, 2026

Last Modified

August 12, 2026

Vendor Advisories for CVE-2026-6727(2)

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 31× in last 7d / 45× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:34 UTCVendor advisory
  3. 2026-08-20 22:34 UTCGHSA enrichment
  4. 2026-08-20 00:53 UTCEG score recompute
  5. 2026-08-20 00:53 UTCVendor advisory
  6. 2026-08-20 00:53 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 03:12 UTCEG score recompute
  9. 2026-08-19 03:12 UTCVendor advisory
  10. 2026-08-19 03:11 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 05:28 UTCEG score recompute
  14. 2026-08-18 05:27 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 07:43 UTCEG score recompute
  17. 2026-08-17 07:43 UTCVendor advisory
  18. 2026-08-17 07:43 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 10:02 UTCEG score recompute
  22. 2026-08-16 10:02 UTCVendor advisory
  23. 2026-08-16 10:02 UTCGHSA enrichment
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 12:22 UTCEG score recompute
Show 20 more
  1. 2026-08-15 12:22 UTCVendor advisory
  2. 2026-08-15 12:22 UTCGHSA enrichment
  3. 2026-08-15 01:31 UTCEPSS rescore
  4. 2026-08-14 14:41 UTCEG score recompute
  5. 2026-08-14 14:41 UTCVendor advisory
  6. 2026-08-14 14:41 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 17:00 UTCEG score recompute
  9. 2026-08-13 17:00 UTCVendor advisory
  10. 2026-08-13 17:00 UTCGHSA enrichment
  11. 2026-08-12 19:19 UTCVendor advisory
  12. 2026-08-12 19:19 UTCGHSA enrichment
  13. 2026-08-12 18:56 UTCEG score recompute 5.90
  14. 2026-08-12 18:56 UTCVendor advisory
  15. 2026-08-12 18:56 UTCGHSA enrichment
  16. 2026-08-12 18:55 UTCMITRE cvelistV5CVSS v3 → 5.9 · severity → MEDIUM
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 16:35 UTCNVD update
  19. 2026-08-11 15:41 UTCEG score recompute
  20. 2026-08-11 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6727?
CVE-2026-6727 is a medium vulnerability published on August 11, 2026. A timing side-channel vulnerability exists in the RSA OAEP decryption implementation. A privileged local attacker with access to the TPM command interface may be able to exploit timing differences to recover information that could allow decryption of ciphertexts encrypted to TPM-managed RSA keys,…
When was CVE-2026-6727 disclosed?
CVE-2026-6727 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-6727 actively exploited?
CVE-2026-6727 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 95.0% of all scored CVEs.
What is the CVSS score of CVE-2026-6727?
CVE-2026-6727 has a CVSS v3.1 base score of 5.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-6727?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6727, 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-6727

Explore →

Is Your Infrastructure Affected by CVE-2026-6727?

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