CVE-2026-65675

HIGHNVD 6.57.1
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. NVD baseline CVSS 6.5; sources differ by 0.6.

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

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

No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.

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

Published

August 11, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-65675

Vendor Advisories for CVE-2026-65675(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 85× in last 7d / 136× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-65675?
CVE-2026-65675 is a high vulnerability published on August 11, 2026. No cwe for this issue in Visual Studio Code CoPilot Chat Extension allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-65675 disclosed?
CVE-2026-65675 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-65675 actively exploited?
CVE-2026-65675 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 60.5% of all scored CVEs.
What is the CVSS score of CVE-2026-65675?
CVE-2026-65675 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-65675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65675, 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-65675

Explore →

Is Your Infrastructure Affected by CVE-2026-65675?

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