CVE-2026-48569

HIGHNVD 5.57.1▲
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. NVD baseline CVSS 5.5; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 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: 5.5Exploit: None knownExposed: 0

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

Improper input validation in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.

CVSS v3
5.5
EG Score
7.1(medium)
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
28%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 25, 2026

Advisory Details (1)

Auto-updated Jun 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-48569

Vendor Advisories for CVE-2026-48569(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 26× in last 7d / 132× 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 321 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-48569?
CVE-2026-48569 is a high vulnerability published on June 9, 2026. Improper input validation in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
When was CVE-2026-48569 disclosed?
CVE-2026-48569 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48569 actively exploited?
CVE-2026-48569 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 72.3% of all scored CVEs.
What is the CVSS score of CVE-2026-48569?
CVE-2026-48569 has a CVSS v3 base score of 5.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-48569?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48569, 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-48569

Explore →

Is Your Infrastructure Affected by CVE-2026-48569?

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

Start Free Scan →Browse All CVEs