Unauthenticated code execution via undisclosed code injection
Published Jul 8, 2025 · Updated Feb 26, 2026
Code injection in Microsoft Azure Monitor Agent before 1.35.1 allows remote attackers to execute code over an adjacent network. Microsoft has not published the affected component or how it improperly generates code from attacker-controlled input. Exploitation requires adjacent-network access, no authentication or user interaction, and high attack complexity; successful exploitation compromises confidentiality, integrity, and availability.
Summary
What happened
Code injection in Microsoft Azure Monitor Agent before 1.35.1 allows remote attackers to execute code over an adjacent network. Microsoft has not published the affected component or how it improperly generates code from attacker-controlled input. Exploitation requires adjacent-network access, no authentication or user interaction, and high attack complexity; successful exploitation compromises confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-47988
- Published
- Jul 8, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Azure Monitor
- Classifications
- CWE-94, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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.1
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.
Weakness, pattern, technique
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