CVE-2026-65768

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

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

Improper limitation of a pathname to a restricted directory ('path traversal') in Microsoft Teams for Android allows an unauthorized attacker to execute code over a network.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 20, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-65768

Vendor Advisories for CVE-2026-65768(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 127× in last 7d / 178× 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 178 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-65768?
CVE-2026-65768 is a critical vulnerability published on August 11, 2026. Improper limitation of a pathname to a restricted directory ('path traversal') in Microsoft Teams for Android allows an unauthorized attacker to execute code over a network.
When was CVE-2026-65768 disclosed?
CVE-2026-65768 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65768 actively exploited?
CVE-2026-65768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.3% of all scored CVEs.
What is the CVSS score of CVE-2026-65768?
CVE-2026-65768 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-65768?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65768, 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-65768

Explore →

Is Your Infrastructure Affected by CVE-2026-65768?

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