CVE-2026-41107

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

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

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

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

External control of file name or path in Microsoft Edge (Chromium-based) allows an unauthorized attacker to disclose information over a network.

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

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated May 15, 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-41107

Vendor Advisories for CVE-2026-41107(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 / 80× 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 241 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41107?
CVE-2026-41107 is a high vulnerability published on May 12, 2026. External control of file name or path in Microsoft Edge (Chromium-based) allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-41107 disclosed?
CVE-2026-41107 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41107 actively exploited?
CVE-2026-41107 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 51.5% of all scored CVEs.
What is the CVSS score of CVE-2026-41107?
CVE-2026-41107 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41107, 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-41107

Explore →

Is Your Infrastructure Affected by CVE-2026-41107?

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

Start Free Scan →Browse All CVEs