CVE-2026-57097

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 6.4 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-14) is not newer than that change (2026-10-08), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
6.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Untrusted search path in Microsoft XML allows an unauthorized attacker to bypass a security feature with a physical attack.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
31
EG Risk 31/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

October 8, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
Patch available. Sources: microsoft.
MicrosoftMentions a patch (unverified)

Security Update Guide - Microsoft Security Response Center

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-57097

Vendor Advisories for CVE-2026-57097(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 8× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 270 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 170 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-57097?
CVE-2026-57097 is a medium-severity vulnerability; its CVE record was published on July 14, 2026. Untrusted search path in Microsoft XML allows an unauthorized attacker to bypass a security feature with a physical attack.
When was CVE-2026-57097 made public?
CVE-2026-57097 was made public on July 14, 2026: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 14, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-57097 actively exploited?
CVE-2026-57097 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57097?
CVE-2026-57097 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-57097?
A fix for CVE-2026-57097 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57097 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-57097

Explore →

Is Your Infrastructure Affected by CVE-2026-57097?

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

Book a Demo →Browse All CVEs