dbcve.org
Azure Monitor AgentApplication · Microsoft

CVE-2026-32168

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 1.35.9 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in Azure Monitor Agent allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Azure Monitor Agent contains an improper input validation flaw that allows a locally authenticated attacker with existing authorized access to manipulate input in a way that leads to privilege escalation. The vulnerability stems from insufficient validation of input data within the agent's processing logic, enabling a local attacker to gain elevated privileges on the affected system.

MitigationApply the vendor patch for Azure Monitor Agent once available, as this is a vulnerability that requires local access and local privilege escalation capabilities. Prioritize patching systems with direct user access and verify the agent continues functioning correctly after updates.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure Monitor AgentApplication
Affected:< 1.35.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Azure Monitor Agent is installed
    Check for Azure Monitor Agent on the system. On Windows, look for 'Azure Monitor Agent' in Programs and Features or check for the service 'AMA' or 'AzureMonitorAgent' in services.msc. On Linux, check for the package via package manager or look for the binary/daemon.
    Affected if The agent is present on the system
  2. Identify installed version of Azure Monitor Agent
    On Windows, run 'Get-Package -Name "Azure Monitor Agent"' via PowerShell, or check the version in Programs and Features. On Linux, run 'dpkg -l | grep azure-monitor-agent' or 'rpm -qa | grep azure-monitor-agent' depending on package manager.
    Affected if The version returned is less than 1.35.9 or cannot be determined (treat as vulnerable)
  3. Verify agent service is running
    Check if the Azure Monitor Agent service is currently active. On Windows, run 'Get-Service -Name AzureMonitorAgent' or check in services.msc. On Linux, run 'systemctl status azure-monitor-agent' or check for the running process.
    Affected if The agent service is running and version is below 1.35.9
  4. Confirm local access context
    Assess whether the system allows local user access or terminal access that would enable an authenticated local attacker to interact with the agent. Check for multiple user accounts or remote access configurations.
    Affected if Local user accounts or terminal access exists on the system where the vulnerable agent version is running

The environment is affected if Azure Monitor Agent is installed with a version prior to 1.35.9 and the agent service is active on a system with local access capabilities.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.35.9 or later
Fixed in 1.35.9
Interim mitigation

Apply the vendor patch for Azure Monitor Agent once available, as this is a vulnerability that requires local access and local privilege escalation capabilities. Prioritize patching systems with direct user access and verify the agent continues functioning correctly after updates.

Recommended fix Moderate confidence

Azure Monitor Agent version 1.35.9 or later

  1. Identify all systems running Azure Monitor Agent versions prior to 1.35.9
  2. For Windows systems: Verify the currently installed version by checking Programs and Features or running 'Get-WmiObject -Class Win32_Product' filtering for Azure Monitor Agent
  3. For Linux systems: Check the installed version using the package manager (e.g., 'dpkg -l' or 'rpm -qa' for ama-linux)
  4. Plan the upgrade during a maintenance window to minimize disruption
  5. Upgrade Azure Monitor Agent to version 1.35.9 or later using your deployment method (e.g., Azure Arcade, manual installer, or management tool)
  6. Verify the upgrade was successful by confirming the new version number post-installation
  7. Confirm that Azure Monitor Agent data collection is functioning normally after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Monitor Agent Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32168 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data