CVE-2025-47988
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 · uneditedImproper control of generation of code ('code injection') in Azure Monitor Agent allows an unauthorized attacker to execute code over an adjacent network.
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 confidenceCode injection vulnerability in Azure Monitor Agent allows an unauthorized attacker to execute arbitrary code over an adjacent network. The vulnerability stems from improper control of code generation within the agent component.
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< 1.35.1CVSS 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Azure Monitor Agent is installedOn Windows, open Programs and Features or check Registry key HKLM\SOFTWARE\Microsoft\Azure Monitor Agent. On Linux, run 'dpkg -l | grep ama' or 'rpm -qa | grep ama'. Verify the Microsoft Azure Monitor Agent or AMA extension is present.Affected if Azure Monitor Agent is installed on the system
-
Identify the installed version numberOn Windows, check the version in Programs and Features details column, or query the registry at HKLM\SOFTWARE\Microsoft\Azure Monitor Agent\AgentVersion. On Linux, run 'scxadmin -version' or check the installed AMA package version.Affected if The version returned is lower than 1.35.1 (for example, 1.34.0, 1.30.2, etc.)
-
Verify the agent service is runningOn Windows, open Services console and check if 'Azure Monitor Agent' service exists and is running, or run 'Get-Service AzureMonitorAgent' via PowerShell. On Linux, run 'systemctl status ama' or check if the AMA process is active.Affected if The agent service is active and the version is below 1.35.1
-
Assess network exposureReview network configuration to determine if the system with Azure Monitor Agent is accessible from untrusted adjacent networks. Check firewall rules, NSG settings, or network segmentation that might allow adjacent network attackers to reach the agent.Affected if The affected agent version is installed and the system has accessible network interfaces from adjacent (non-local) networks
You are affected if Azure Monitor Agent version is installed and the detected version is lower than 1.35.1, with the agent running and accessible from adjacent networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.35.1
Apply available security updates for Azure Monitor Agent as released by Microsoft, and restrict network access to only trusted adjacent networks to reduce attack surface.
Azure Monitor Agent version 1.35.1 or later
- Verify current Azure Monitor Agent version by checking the agent configuration or VM extensions in Azure Portal
- Navigate to the Virtual Machine or Virtual Machine Scale Set in Azure Portal where the agent is installed
- Update the Azure Monitor Agent extension to version 1.35.1 or later using the Azure Portal, Azure CLI, or ARM template
- For Azure Arc-enabled servers, update the Azure Monitor Agent extension through the Azure Arc portal or CLI
- After upgrade, verify the agent is running and connected by checking the 'Insights' section in Azure Monitor
- Confirm the agent version has been updated to 1.35.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47988 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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