SYSTEM code execution via ExtensionService hijacking
Published Oct 14, 2025 · Updated Oct 14, 2025
Improper access control in Azure Connected Machine agent before 1.57 allows local users to execute code as SYSTEM on Windows. The ExtensionService accepts unverified metadata and access tokens from the local HIMDS HTTP endpoint, allowing a port-squatting listener to redirect it to an attacker-controlled tenant and deploy a malicious extension. Exploitation requires a low-privileged local user to trigger MSI repair, win the listener race, and control an Azure tenant.
Summary
What happened
Improper access control in Azure Connected Machine agent before 1.57 allows local users to execute code as SYSTEM on Windows. The ExtensionService accepts unverified metadata and access tokens from the local HIMDS HTTP endpoint, allowing a port-squatting listener to redirect it to an attacker-controlled tenant and deploy a malicious extension. Exploitation requires a low-privileged local user to trigger MSI repair, win the listener race, and control an Azure tenant.
The record
- CVE
- CVE-2025-47989
- Published
- Oct 14, 2025
- Updated
- Oct 14, 2025
- Vendor
- Microsoft
- Product
- Azure Connected Machine agent
- Classifications
- CWE-284, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 14, 2025CVE publishedPublication date reported by the CVE source.
- Oct 14, 2025Record 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 <xxxxx
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
- ExtensionService hijacking proof of conceptfunctional · demonstrated
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