CVE-2026-6727

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM 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.2%CVSS: 5.9Exploit: None knownExposed services: Not assessed

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

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.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 11, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic
https://trustedcomputinggroup.org/wp-content/uploads/Extended-vrt0010-11-guidance_V1.pdf
generic
https://trustedcomputinggroup.org/wp-content/uploads/VRT0011-Advisory_Final-1.pdf
generic

Security | Trusted Computing Group

https://trustedcomputinggroup.org/about/security/

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libtpms0.10.1-1 ... 0.9.2-3.2+hurd.1 (11 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libtpms0.10.1-1 ... 0.9.2-3.2+hurd.1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libtpms0.10.1-1 ... 0.9.2-3.2+hurd.1 (9 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 100× 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.

Showing the most recent 100 of 201 total refreshes for this CVE.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 22:46 UTCVendor advisory
  3. 2026-10-04 22:46 UTCGHSA enrichment
  4. 2026-10-03 21:03 UTCEG score recompute
  5. 2026-10-03 21:03 UTCVendor advisory
  6. 2026-10-03 21:03 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-02 17:56 UTCEPSS rescore
  9. 2026-10-02 08:43 UTCEG score recompute
  10. 2026-10-02 08:43 UTCVendor advisory
  11. 2026-10-02 08:43 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-09-30 22:18 UTCEG score recompute
  14. 2026-09-30 22:18 UTCVendor advisory
  15. 2026-09-30 22:18 UTCGHSA enrichment
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-29 05:52 UTCEG score recompute
  18. 2026-09-29 05:52 UTCVendor advisory
  19. 2026-09-29 05:52 UTCGHSA enrichment
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-28 08:11 UTCEG score recompute
  22. 2026-09-28 08:11 UTCVendor advisory
  23. 2026-09-28 08:11 UTCGHSA enrichment
  24. 2026-09-27 13:48 UTCEPSS rescore
  25. 2026-09-27 10:22 UTCEG score recompute
Show 75 more
  1. 2026-09-27 10:22 UTCVendor advisory
  2. 2026-09-27 10:22 UTCGHSA enrichment
  3. 2026-09-26 15:59 UTCEPSS rescore
  4. 2026-09-25 03:55 UTCEG score recompute
  5. 2026-09-25 03:55 UTCVendor advisory
  6. 2026-09-25 03:55 UTCGHSA enrichment
  7. 2026-09-23 21:03 UTCEG score recompute
  8. 2026-09-23 21:03 UTCVendor advisory
  9. 2026-09-23 21:03 UTCGHSA enrichment
  10. 2026-09-23 17:54 UTCEPSS rescore
  11. 2026-09-22 21:13 UTCEG score recompute
  12. 2026-09-22 21:13 UTCVendor advisory
  13. 2026-09-22 21:13 UTCGHSA enrichment
  14. 2026-09-21 21:11 UTCEG score recompute
  15. 2026-09-21 21:11 UTCVendor advisory
  16. 2026-09-21 21:11 UTCGHSA enrichment
  17. 2026-09-21 21:09 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-20 19:37 UTCVendor advisory
  20. 2026-09-20 19:36 UTCGHSA enrichment
  21. 2026-09-19 21:19 UTCEG score recompute
  22. 2026-09-19 21:19 UTCVendor advisory
  23. 2026-09-19 21:19 UTCGHSA enrichment
  24. 2026-09-18 23:12 UTCEG score recompute
  25. 2026-09-18 23:12 UTCVendor advisory
  26. 2026-09-18 23:12 UTCGHSA enrichment
  27. 2026-09-18 19:28 UTCEPSS rescore
  28. 2026-09-18 01:31 UTCEG score recompute
  29. 2026-09-18 01:31 UTCVendor advisory
  30. 2026-09-18 01:31 UTCGHSA enrichment
  31. 2026-09-17 03:50 UTCEG score recompute
  32. 2026-09-17 03:50 UTCVendor advisory
  33. 2026-09-17 03:50 UTCGHSA enrichment
  34. 2026-09-16 14:08 UTCEPSS rescore
  35. 2026-09-16 05:15 UTCEPSS rescore
  36. 2026-09-16 05:07 UTCVendor advisory
  37. 2026-09-16 05:07 UTCGHSA enrichment
  38. 2026-09-15 06:30 UTCEG score recompute
  39. 2026-09-15 06:30 UTCVendor advisory
  40. 2026-09-15 06:30 UTCGHSA enrichment
  41. 2026-09-15 03:12 UTCEPSS rescore
  42. 2026-09-14 07:12 UTCEG score recompute
  43. 2026-09-14 07:12 UTCVendor advisory
  44. 2026-09-14 07:12 UTCGHSA enrichment
  45. 2026-09-13 09:31 UTCEG score recompute
  46. 2026-09-13 09:31 UTCVendor advisory
  47. 2026-09-13 09:31 UTCGHSA enrichment
  48. 2026-09-12 15:02 UTCEPSS rescore
  49. 2026-09-12 11:50 UTCEG score recompute
  50. 2026-09-12 11:50 UTCVendor advisory
  51. 2026-09-12 11:50 UTCGHSA enrichment
  52. 2026-09-11 14:53 UTCEPSS rescore
  53. 2026-09-11 14:04 UTCEG score recompute
  54. 2026-09-11 14:04 UTCGHSA enrichment
  55. 2026-09-10 15:50 UTCEG score recompute
  56. 2026-09-10 15:50 UTCGHSA enrichment
  57. 2026-09-10 09:35 UTCEPSS rescore
  58. 2026-09-09 18:02 UTCEG score recompute
  59. 2026-09-09 18:02 UTCVendor advisory
  60. 2026-09-09 18:02 UTCGHSA enrichment
  61. 2026-09-08 22:01 UTCEPSS rescore
  62. 2026-09-08 15:24 UTCVendor advisory
  63. 2026-09-08 15:24 UTCGHSA enrichment
  64. 2026-09-07 18:55 UTCEG score recompute
  65. 2026-09-07 18:55 UTCVendor advisory
  66. 2026-09-07 18:55 UTCGHSA enrichment
  67. 2026-09-07 16:01 UTCEPSS rescore
  68. 2026-09-06 21:15 UTCEG score recompute
  69. 2026-09-06 21:15 UTCVendor advisory
  70. 2026-09-06 21:15 UTCGHSA enrichment
  71. 2026-09-06 13:47 UTCEPSS rescore
  72. 2026-09-05 23:24 UTCEG score recompute
  73. 2026-09-05 23:24 UTCVendor advisory
  74. 2026-09-05 23:24 UTCGHSA enrichment
  75. 2026-09-05 15:31 UTCEPSS rescore

Related CVEs(same product + same CWE)

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 on August 11, 2026, with the most recent update on September 8, 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.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-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?
No fix for CVE-2026-6727 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-6727 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs