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 — 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: 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

July 23, 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 18× in last 7d / 98× 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 192 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 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-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.4% 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