What is the CVSS score of CVE-2026-47299?

CVE-2026-47299 has a CVSS 3.1 base score of 7.2 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.0%.

Which versions of Azure Monitor Agent are affected by CVE-2026-47299?

The Azure Monitor Agent Linux Extension (versions below 1.43) is vulnerable to command injection attacks by authenticated high-privilege users, enabling attackers to compromise host systems and…. A patch is available.

How to fix or mitigate CVE-2026-47299?

Within 24 hours, inventory all Linux servers running Azure Monitor Agent and document current installed versions. Within 7 days, upgrade all affected instances (versions 1.0.0 through pre-1.43) to version 1.43 or later according to Microsoft's MSRC advisory, prioritizing production systems. Within 30 days, complete the upgrade across all environments and validate that monitoring functionality is restored and operational.

Azure Monitor Agent CVE-2026-47299

EUVD-2026-56305 HIGH

Command Injection (CWE-77)

2026-08-11 secure@microsoft.com

GHSA-87m8-66q7-8p58

Command Injection Microsoft Azure Monitor Agent

7.2

CVSS 3.1 · Vendor: microsoft

Severity by source

Vendor (microsoft) PRIMARY

7.2 HIGH

AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

ENISA EUVD

HIGH

qualitative

vuln.today AI

7.2 HIGH

Network-delivered command injection requiring pre-existing high-privilege access; unchanged scope; full C/I/A impact because successful injection with privilege escalation yields complete host control.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 11, 2026 - 21:24 vuln.today

Patch available

Aug 11, 2026 - 18:19 EUVD

CVE Published

Aug 11, 2026 - 17:17 nvd

HIGH 7.2

DescriptionCVE.org

Improper neutralization of special elements used in a command ('command injection') in Azure Monitor Agent allows an authorized attacker to elevate privileges over a network.

AnalysisAI

Command injection in Azure Monitor Agent Linux Extension (versions 1.0.0 through pre-1.43) enables privilege escalation over a network by an authorized attacker with high-privilege access. The CVSS:3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) confirms network-based exploitation yielding full confidentiality, integrity, and availability impact on the affected host. No public exploit code or CISA KEV listing has been identified at time of analysis; a vendor patch is confirmed available from Microsoft MSRC.

Technical ContextAI

Azure Monitor Agent is Microsoft's telemetry and log collection service deployed as a Linux VM extension on Azure-hosted and hybrid Linux machines. CWE-77 (Improper Neutralization of Special Elements used in a Command) indicates the root cause is insufficient sanitization of attacker-controlled input before it is passed to an underlying shell or command interpreter - a classic command injection pattern. Because the agent runs in a privileged context on the host OS as a system extension, unsanitized input reaching a shell invocation can be leveraged to execute arbitrary commands at elevated privilege levels. The affected component is specifically the Linux Extension variant (EUVD-confirmed CPE-equivalent: Azure Monitor Agent Linux Extension), not the Windows counterpart.

RemediationAI

Upgrade Azure Monitor Agent Linux Extension to version 1.43 or later; this is the vendor-confirmed fix per Microsoft MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-47299. If immediate patching is operationally constrained, restrict the pool of principals holding high-privilege access to the Azure Monitor Agent configuration and management interface - since exploitation requires PR:H, reducing privileged access directly reduces attack surface, though this is not a substitute for patching. Additionally, enable Azure Monitor diagnostic logging and audit shell-level command execution on affected hosts for anomalous invocations, which can serve as a detection compensating control. Network-level restrictions on agent management traffic may reduce exposure but do not eliminate the vulnerability if a privileged credential is compromised.