Authenticated code execution via out-of-bounds write
Published Dec 9, 2025 · Updated Apr 16, 2026
Out-of-bounds write in Microsoft Azure Monitor Agent before 1.35.9 allows remote authenticated users to execute code over a network. Microsoft identifies an incorrect buffer-size calculation leading to an out-of-bounds write but has not disclosed the affected parser, function, input, or reachable service. Successful exploitation requires low-privileged authorization and executes code in the agent process, exposing the host to data access, alteration, and service interruption.
Summary
What happened
Out-of-bounds write in Microsoft Azure Monitor Agent before 1.35.9 allows remote authenticated users to execute code over a network. Microsoft identifies an incorrect buffer-size calculation leading to an out-of-bounds write but has not disclosed the affected parser, function, input, or reachable service. Successful exploitation requires low-privileged authorization and executes code in the agent process, exposing the host to data access, alteration, and service interruption.
The record
- CVE
- CVE-2025-62550
- Published
- Dec 9, 2025
- Updated
- Apr 16, 2026
- Vendor
- Microsoft
- Product
- Azure Monitor
- Classifications
- CWE-787, CWE-131
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- Apr 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.35.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo