Security Resilience

CVE-2026-32192

Deserialization in Microsoft Azure Monitor Agent ≤ 1.41.0

Published
14 April 2026
Modified
07 May 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.025 85th percentile
Risk Priority 61 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-32192 is a high-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Microsoft Azure Monitor Agent. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-32192 is a deserialization of untrusted data vulnerability (CWE-502) in the Azure Monitor Agent. Published on 2026-04-14, it carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact on confidentiality, integrity, and availability.

A local attacker with low privileges (PR:L) can exploit this issue with low complexity and no user interaction required. Successful exploitation allows privilege escalation on the affected system.

Microsoft's update guide provides details on mitigation and patching for this vulnerability: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32192.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Deserialization of untrusted data in Azure Monitor Agent allows an authorized attacker to elevate privileges locally.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-59285Same product: Microsoft Azure Monitor Agent
CVE-2024-38018Same vendor: Microsoft
CVE-2023-21779Same vendor: Microsoft
CVE-2024-38024Same vendor: Microsoft
CVE-2025-55232Same vendor: Microsoft
CVE-2025-54897Same vendor: Microsoft
CVE-2024-38094Same vendor: Microsoft
CVE-2023-21703Same vendor: Microsoft
CVE-2026-65772Same vendor: Microsoft
CVE-2026-85900Same vendor: Microsoft

Affected Assets

microsoft
azure monitor agent
≤ 1.41.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

References