Azure CycleCloud EUVD-2026-100318

Exploitation requires the attacker to already hold valid low-privileged credentials on an Azure CycleCloud instance (PR:L) and to have local access to the system (AV:L), and it additionally depends on user interaction (UI:R) - meaning a user or operator must perform some action for the injected command to execute. The concrete injection point (the specific CycleCloud feature or input field that forwards data into an OS command) is not named in the description beyond CWE-78 os command injection. Limiting factors that reduce real-world risk: no network-facing unauthenticated path (local vector only), a required authentication level, and a required victim action, all of which narrow exploitation to insiders or attackers who have already gained a foothold plus the ability to trigger the interaction.

This is a moderate-priority issue, not a top-tier emergency. The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3) describes a locally-exploitable OS command injection requiring an already-authenticated low-privileged user AND user interaction - three distinct barriers (local access, valid credentials, a victim action) that substantially lower real-world exploitability despite the HIGH confidentiality/integrity/availability impact. No EPSS score, KEV listing, SSVC decision, or POC is present in the supplied intelligence, so there is no signal of active exploitation or published exploit code; exploitation status is therefore 'no public exploit identified at time of analysis.' The signals are internally consistent (local vector, low-priv auth, meaningful impact) with no contradiction between the vector and the description, which both point to a local, authenticated privilege-escalation-style code execution. The main uncertainty is the absence of exploitation-probability telemetry (EPSS/KEV) and any affected-version data; the single MSRC reference was not independently retrievable here, so patch and version details are unconfirmed. Overall: patch in the normal cycle rather than treat as drop-everything, since the local + authenticated + user-interaction preconditions make widespread opportunistic exploitation unlikely.

A low-privileged but authenticated user of an Azure CycleCloud deployment supplies crafted input (or induces an operator to act on it, satisfying the user-interaction requirement) that is passed unsanitized into an OS command, causing arbitrary commands to run in the local context of the CycleCloud process. This could let the attacker escalate privileges or compromise the cluster orchestration host. No public proof-of-concept or exploit code is identified in the available data.