EUVD-2026-22559
GHSA-2vp6-3rx5-75mf
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Lifecycle Timeline
6DescriptionCVE.org
Improper input validation in Azure Monitor Agent allows an authorized attacker to elevate privileges locally.
AnalysisAI
Local privilege escalation in Azure Monitor Agent versions prior to 1.35.9 enables authenticated users to gain elevated system privileges through improper input validation flaws. The vulnerability requires low attack complexity and no user interaction, allowing low-privileged attackers with local access to achieve complete system compromise (high confidentiality, integrity, and availability impact). EPSS data not available; no public exploit identified at time of analysis; SSVC framework indicates total technical impact but no active exploitation and non-automatable exploitation vector.
Technical ContextAI
Azure Monitor Agent is Microsoft's telemetry and monitoring solution deployed on Windows and Linux systems to collect logs, metrics, and performance data. This vulnerability stems from CWE-20 (Improper Input Validation), where the agent fails to properly sanitize or validate user-controlled input before processing it in a privileged context. The affected component (cpe:2.3:a:microsoft:azure_monitor:*:*:*:*:*:*:*:*) likely processes configuration files, command-line parameters, or inter-process communication messages without sufficient validation checks. When the agent runs with elevated system privileges (common for monitoring solutions requiring deep system access), the input validation flaw creates a local privilege escalation vector. The local attack vector (AV:L) indicates exploitation requires prior access to the system, while low attack complexity (AC:L) suggests the exploitation technique is straightforward once access is obtained.
RemediationAI
Upgrade Azure Monitor Agent to version 1.35.9 or later, which contains the vendor-released patch addressing the input validation vulnerability. Microsoft has released the security update through standard distribution channels including Windows Update, Azure portal agent management, and Linux package repositories. Administrators should deploy the patched version using their existing agent management workflow, whether through Azure Policy, Azure Arc, or manual package updates. For environments where immediate patching is not feasible, implement compensating controls including restricting local user access to systems running Azure Monitor Agent, enabling enhanced monitoring for privilege escalation attempts through audit logs, and applying principle of least privilege to limit the number of accounts with local access. Complete remediation guidance and update packages are available in the official Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32168. No workaround fully mitigates the vulnerability; patching to version 1.35.9 or later is the only complete remediation.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today