CVE-2026-69320

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. The CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
8.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: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper neutralization of special elements used in an os command ('os command injection') in Visual Studio Code allows an unauthorized attacker to execute code over a network.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
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
57th
KEV
Not listed

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.

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

October 8, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

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

Vendor Advisories for CVE-2026-69320(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 17× in last 7d / 120× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 404 refreshes 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 304 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-69320?
CVE-2026-69320 is a high-severity vulnerability; its CVE record was published on August 11, 2026. Improper neutralization of special elements used in an os command ('os command injection') in Visual Studio Code allows an unauthorized attacker to execute code over a network.
When was CVE-2026-69320 made public?
CVE-2026-69320 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-69320 actively exploited?
CVE-2026-69320 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69320?
CVE-2026-69320 has a CVSS base score of 8.8 (the CNA's own assessment, by microsoft; NVD's own analysis pending).
How do I remediate CVE-2026-69320?
A fix for CVE-2026-69320 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69320 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-69320

Explore →

Is Your Infrastructure Affected by CVE-2026-69320?

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

Book a Demo →Browse All CVEs