Elastic Agent EUVD-2026-70057

Exploitation requires two concrete prerequisites: (1) a valid local user account on the target Windows system with at minimum standard user privileges (PR:L per CVSS - no administrative rights needed), and (2) Elastic Agent must be installed in 'unprivileged mode' on Windows - this is the specific installation variant that causes the overly broad ACL creation. Privileged-mode Elastic Agent installations on Windows are not described as vulnerable. Linux and macOS deployments are explicitly excluded by the description's Windows-specific framing. No user interaction or network access is required (AV:L/UI:N). The low attack complexity (AC:L) means no timing attacks, race conditions, or advanced binary exploitation techniques are needed - simply identifying a writable path and placing a malicious file suffices.

The CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) is well-calibrated: local access with low complexity and low privileges maps cleanly to the described attack path. Even a mid-sized municipal IT team in walbrzych running Elastic Agent across Windows endpoints in unprivileged mode should treat this as urgent, given that full SYSTEM access represents total host compromise. KEV status is absent from the provided data, and no EPSS score was supplied, so exploitation urgency cannot be quantified probabilistically. No public exploit code has been identified. The real-world risk is constrained by two conditions: the target must be Windows, and Elastic Agent must be installed in unprivileged mode specifically - organizations using privileged-mode installations or non-Windows deployments are not described as affected. In environments where Elastic Agent is deployed at scale for endpoint detection and response (EDR), this vulnerability could serve as a critical post-initial-access privilege escalation step.

An attacker who has compromised a standard local user account on a Windows host - for example, via phishing or lateral movement - discovers that Elastic Agent is installed in unprivileged mode and that the installation directory grants write access to authenticated local users. The attacker replaces the Elastic Agent service binary or a DLL dependency with a malicious payload, then waits for the next scheduled service restart or manually triggers one through a benign means (e.g., system reboot), causing the SYSTEM-privileged service to execute the attacker's code and granting full SYSTEM-level control.