Microsoft XML CVE-2026-57097

Physical access to the target machine is the mandatory prerequisite - this vulnerability cannot be exploited remotely under any configuration. The CVSS vector AV:P explicitly encodes this requirement. An attacker must be physically present to manipulate the file system or introduce removable media that plants a malicious binary in the search path ahead of the legitimate MSXML library. No prior authentication to Windows is required (PR:N), because physical presence substitutes for logical access control. No user interaction is needed after the attacker has planted the malicious file (UI:N). Exploitation is limited by physical security controls: locked workstations with disabled removable media boot, UEFI password protection, BitLocker-enforced volumes, and Secure Boot all independently raise the bar for this attack path. The vulnerability does not appear to require any special non-default software configuration beyond the attacker gaining physical access.

Despite a CVSS base score of 6.8 and a High confidentiality, integrity, and availability impact triad, the real-world exploitation risk is substantially constrained by the physical attack vector (AV:P in the provided CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H vector). Exploitation cannot be automated or conducted remotely, which SSVC independently confirms with Automatable: no. The EPSS score of 0.25% placing this at the 16th percentile further corroborates minimal exploitation probability in practice. CVE-2026-57097 is not listed in the CISA KEV catalog, and SSVC records Exploitation as none. The Technical Impact rated total reflects worst-case post-exploitation outcome but is gated entirely behind the physical access prerequisite. This is a textbook case of a high-CVSS-but-low-operational-risk vulnerability: the impact metrics inflate the score, but physical access as the entry point means most enterprise environments face negligible threat from external actors. The primary risk population is kiosk systems, physically accessible workstations, shared lab or library machines, or devices subject to supply-chain or insider physical tampering.

An attacker with physical access to an unattended or unlocked Windows workstation boots from a USB drive or inserts removable media containing a malicious DLL crafted to impersonate a legitimate MSXML dependency, placing it in a directory that takes precedence in the search path. When a Windows process or application subsequently loads the MSXML component, the malicious DLL is resolved instead of the legitimate system library, allowing the attacker to execute arbitrary code in the context of the loading process and bypass Windows security enforcement mechanisms. No public exploit code has been identified at time of analysis.