CVE-2026-57983

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

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

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

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

Improper authorization in Microsoft Edge (Chromium-based) allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.7
EG Score
8.7(high)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
38.2%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 24, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-57983(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 17× 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.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57983?

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

Start Free Scan →Browse All CVEs