Quick answers
- Is CVE-2026-32204 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32204 being exploited in the wild.
- How severe is CVE-2026-32204?
- High severity, with a CVSS score of 7.8, published 12 May 2026.
- Which products and versions are affected?
- Microsoft Azure Monitor Agent 1.0.0 up to (excluding) 1.14.0.
- Is there a fix for CVE-2026-32204?
- A patch was published on 2026-06-18: NVD updated with fix version 1.14.0 information Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32204 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-32204?
- Check whether you run Microsoft Azure Monitor Agent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A local privilege escalation vulnerability exists in the Microsoft Azure Monitor Agent due to improper validation of externally controlled file names or paths (CWE-73/CWE-610). An authenticated attacker with low-privileged local access can manipulate file system references used by the agent to execute code or perform actions with the higher privileges of the agent service. The vulnerability affects versions prior to 1.14.0. Successful exploitation grants the attacker full SYSTEM or root-level permissions on the host, depending on the operating system. Microsoft has released version 1.14.0 to address this issue.
Affected products
- Microsoft Azure Monitor Agent 1.0.0 up to (excluding) 1.14.0
Timeline
- 2026-05-12: disclosed: Initial disclosure by Microsoft
- 2026-05-12: advisory: MSRC advisory published
- 2026-06-18: patched: NVD updated with fix version 1.14.0 information