CVE-2026-65768

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.9% (61st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.8 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-11) is not newer than that change (2026-11-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-56290 (ENISA EUVD) · GHSA-pcpc-w22h-9cxr (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.9% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.9%
EPSS %ILE
61st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 11, 2026

Last Modified

November 10, 2026

Advisory Details (1)

Auto-updated Nov 7, 2026
Patch available. Sources: microsoft.
Microsoft

Security Update Guide - Microsoft Security Response Center

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 18× in last 7d / 82× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 817 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 717 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 23:38 UTCEchelonGraph re-scored
  2. 2026-11-12 23:38 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  4. 2026-11-11 22:53 UTCEchelonGraph re-scored
  5. 2026-11-11 22:53 UTCVendor advisory
  6. 2026-11-11 22:53 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  8. 2026-11-10 22:07 UTCEchelonGraph re-scored
  9. 2026-11-10 22:07 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  11. 2026-11-10 00:57 UTCEchelonGraph re-scored
  12. 2026-11-10 00:57 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  13. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  14. 2026-11-09 00:12 UTCEchelonGraph re-scored
  15. 2026-11-09 00:12 UTCVendor advisory
  16. 2026-11-09 00:12 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  17. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  18. 2026-11-07 23:25 UTCEchelonGraph re-scored
  19. 2026-11-07 23:25 UTCVendor advisory
  20. 2026-11-07 23:25 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  21. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  22. 2026-11-06 22:40 UTCEchelonGraph re-scored
  23. 2026-11-06 22:40 UTCVendor advisory
  24. 2026-11-06 22:40 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  25. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.9% · 61st percentile
Show 75 more
  1. 2026-11-05 21:54 UTCEchelonGraph re-scored
  2. 2026-11-05 21:54 UTCVendor advisory
  3. 2026-11-05 21:54 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  5. 2026-11-04 21:09 UTCEchelonGraph re-scored
  6. 2026-11-04 21:09 UTCVendor advisory
  7. 2026-11-04 21:09 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  8. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.9% · 61st percentile
  9. 2026-11-03 20:23 UTCEchelonGraph re-scored
  10. 2026-11-03 20:23 UTCVendor advisory
  11. 2026-11-03 20:23 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  13. 2026-11-02 19:38 UTCEchelonGraph re-scored
  14. 2026-11-02 19:38 UTCVendor advisory
  15. 2026-11-02 19:38 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  17. 2026-11-01 18:52 UTCEchelonGraph re-scored
  18. 2026-11-01 18:52 UTCVendor advisory
  19. 2026-11-01 18:52 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  21. 2026-10-31 18:07 UTCEchelonGraph re-scored
  22. 2026-10-31 18:07 UTCVendor advisory
  23. 2026-10-31 18:07 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  25. 2026-10-30 17:21 UTCEchelonGraph re-scored
  26. 2026-10-30 17:21 UTCVendor advisory
  27. 2026-10-30 17:21 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  29. 2026-10-29 20:56 UTCEchelonGraph re-scored
  30. 2026-10-29 20:56 UTCVendor advisory
  31. 2026-10-29 20:56 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  32. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  33. 2026-10-28 20:10 UTCEchelonGraph re-scored
  34. 2026-10-28 20:10 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  35. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  36. 2026-10-28 00:12 UTCEchelonGraph re-scored
  37. 2026-10-28 00:11 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  38. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  39. 2026-10-26 23:24 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-10-26 22:58 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  41. 2026-10-26 22:42 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  42. 2026-10-26 21:46 UTCEchelonGraph re-scored
  43. 2026-10-26 21:45 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  44. 2026-10-26 20:20 UTCEchelonGraph re-scored
  45. 2026-10-26 20:20 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  47. 2026-10-25 17:46 UTCEchelonGraph re-scored
  48. 2026-10-25 17:46 UTCVendor advisory
  49. 2026-10-25 17:46 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  50. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  51. 2026-10-25 14:11 UTCEchelonGraph re-scored
  52. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  53. 2026-10-24 16:26 UTCEchelonGraph re-scored
  54. 2026-10-24 16:26 UTCVendor advisory
  55. 2026-10-24 16:26 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  56. 2026-10-23 19:28 UTCEchelonGraph re-scored
  57. 2026-10-23 19:28 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  59. 2026-10-22 21:44 UTCEchelonGraph re-scored
  60. 2026-10-22 21:44 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  62. 2026-10-21 20:57 UTCEchelonGraph re-scored
  63. 2026-10-21 20:57 UTCVendor advisory
  64. 2026-10-21 20:57 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  66. 2026-10-20 21:52 UTCEchelonGraph re-scored
  67. 2026-10-20 21:52 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  68. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  69. 2026-10-19 21:06 UTCEchelonGraph re-scored
  70. 2026-10-19 21:06 UTCVendor advisory
  71. 2026-10-19 21:06 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  73. 2026-10-18 19:56 UTCEchelonGraph re-scored
  74. 2026-10-18 19:56 UTCVendor advisory
  75. 2026-10-18 19:56 UTCGHSA enrichmentGHSA-pcpc-w22h-9cxr · GitHub severity HIGH · GitHub CVSS 8.8

Frequently asked(5)

What is CVE-2026-65768?
CVE-2026-65768 is a critical-severity vulnerability; its CVE record was 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 made public?
CVE-2026-65768 was made public on August 11, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on August 11, 2026. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-65768 actively exploited?
CVE-2026-65768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (61st percentile of EPSS-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?
A fix for CVE-2026-65768 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65768 are linked in the Vendor Advisories panel on this page.

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.