CVE-2026-57975

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

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

Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

CVSS v3
7.5
EG Score
7.5(high)
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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
35.1%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jul 6, 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-57975

Vendor Advisories for CVE-2026-57975(2)

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 16× in last 7d / 91× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-57975?
CVE-2026-57975 is a high vulnerability published on July 3, 2026. Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
When was CVE-2026-57975 disclosed?
CVE-2026-57975 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57975 actively exploited?
CVE-2026-57975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57975?
CVE-2026-57975 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-57975?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57975, 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-57975

Explore →

Is Your Infrastructure Affected by CVE-2026-57975?

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

Start Free Scan →Browse All CVEs