CVE-2026-47292

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to elevate privileges locally.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
29.3%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 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-47292

Vendor Advisories for CVE-2026-47292(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 8× in last 7d / 104× 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 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-47292?
CVE-2026-47292 is a high vulnerability published on June 9, 2026. Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to elevate privileges locally.
When was CVE-2026-47292 disclosed?
CVE-2026-47292 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47292 actively exploited?
CVE-2026-47292 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47292?
CVE-2026-47292 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-47292?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47292, 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-47292

Explore →

Is Your Infrastructure Affected by CVE-2026-47292?

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