dbcve.org
Azure Monitor AgentApplication · Microsoft

CVE-2025-59285

HIGH · 7.0 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 1.36.3 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Deserialization of untrusted data 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

A deserialization vulnerability in Azure Monitor Agent allows an authorized attacker to perform local privilege escalation by exploiting unsafe deserialization of untrusted data within the agent's processing pipeline.

MitigationApply the vendor-released security update for Azure Monitor Agent to remediate the deserialization vulnerability; verify that affected systems receive the patched version.

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.36.3

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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. Identify Azure Monitor Agent installation
    Check for Azure Monitor Agent (AMA) installation using: On Windows, check 'Programs and Features' or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*Azure Monitor*"}'; On Linux, check package manager listings like 'dpkg -l | grep azure-monitor' or 'rpm -qa | grep azure-monitor'
    Affected if Azure Monitor Agent is installed on the system
  2. Determine installed Azure Monitor Agent version
    Run version check command: On Windows, 'Get-ItemProperty HKLM:\SOFTWARE\Microsoft\AzureMonitorAgent\DisplayName' or check the agent'sAbout page in MMA; On Linux, run 'cat /var/opt/microsoft/azuremonitoragent/config/agentConfig.json' or check via '/opt/microsoft/azuremonitoragent/bin/azuremonitoragent --version' if available
    Affected if Unable to retrieve version information or version is below 1.36.3
  3. Confirm vulnerability applicability
    Review Azure Monitor Agent status and configuration to confirm the agent is active and processing data: On Windows, check 'Services' for 'Azure Monitor Agent' running status; On Linux, check service status via 'systemctl status azuremonitoragent' or 'service azuremonitoragent status'
    Affected if Agent is installed and running (the deserialization flaw exists in the agent's processing pipeline when active)

The environment is affected if Azure Monitor Agent is installed and running with a version lower than 1.36.3, as this is a local privilege escalation vulnerability in the agent's deserialization processing.

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.36.3 or later
Fixed in 1.36.3
Interim mitigation

Apply the vendor-released security update for Azure Monitor Agent to remediate the deserialization vulnerability; verify that affected systems receive the patched version.

Recommended fix High confidence

Azure Monitor Agent version 1.36.3 or later

  1. Identify the current installed version of Azure Monitor Agent on the target system
  2. Download Azure Monitor Agent version 1.36.3 or later from the official Microsoft download center or Azure portal
  3. Stop the Azure Monitor Agent service before upgrading
  4. Install the updated Azure Monitor Agent version 1.36.3 or newer using the appropriate installer for your OS (MSI for Windows, package for Linux)
  5. Verify the installation completed successfully and confirm the new version is 1.36.3 or later
  6. Restart the Azure Monitor Agent service

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59285 — 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-2025-59285 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