CVE-2026-41109

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

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

Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub Copilot and Visual Studio allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

May 12, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated May 12, 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-41109

Vendor Advisories for CVE-2026-41109(1)

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 9× in last 7d / 50× 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 245 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41109?
CVE-2026-41109 is a high vulnerability published on May 12, 2026. Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub Copilot and Visual Studio allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-41109 disclosed?
CVE-2026-41109 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41109 actively exploited?
CVE-2026-41109 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.5% of all scored CVEs.
What is the CVSS score of CVE-2026-41109?
CVE-2026-41109 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41109?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41109, 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-41109

Explore →

Is Your Infrastructure Affected by CVE-2026-41109?

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