A new critical vulnerability (CVE-2026-105014) has been disclosed in Azure Pipelines, allowing an unauthorized attacker to execute code over a network. Microsoft’s Security Response Center (MSRC) published the details on October 22, 2026, alongside related security updates.

What the vulnerability is

CVE-2026-105014 is a command injection flaw classified under CWE-77 (Improper Neutralization of Special Elements used in a Command). The vulnerability type is listed as “Improper neutralization of special elements used in a command (command injection)” in the MSRC CVSS vector description.

Key details:

  • Impact: Remote Code Execution
  • Max Severity: Critical
  • CVSS Base Score: 9.1 / Temporal Score: 8.2
  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
  • Confidentiality: High
  • Integrity: High
  • Availability: None
  • Exploit Code Maturity: Proof-of-Concept
  • Remediation Level: Official Fix
  • Report Confidence: Confirmed

The executive summary from MSRC states: “Improper neutralization of special elements used in a command (command injection) in Azure Pipelines allows an unauthorized attacker to execute code over a network.”

Why this matters for CI/CD

Azure Pipelines is a foundational development tool used by organizations worldwide to build, test, and deploy applications. A remote code execution vulnerability of this severity means that any attacker with access to the pipeline input surface could execute arbitrary code on build agents.

This is particularly concerning because:

  • The attack requires no privileges or user interaction (CVSS PR:N UI:N)
  • The attack complexity is low, meaning exploitation is straightforward
  • A proof-of-concept exploit is already available
  • The vulnerability affects the platform’s confidentiality and integrity at a high level

For multi-tenant Azure DevOps Services customers, a successful exploit could potentially have cross-tenant implications if build agents are not properly isolated.

What to do now

MSRC notes that this vulnerability has already been fully mitigated by Microsoft. There is no action required for users of the Azure Pipelines cloud service. The purpose of the CVE disclosure is to provide transparency.

For organizations running Azure DevOps Server (on-premises), check your Microsoft Support Lifecycle page for applicable patches and updates.

Recommended actions for administrators:

  1. Verify whether you are running Azure DevOps Services (cloud) or Azure DevOps Server (on-premises)
  2. For on-premises deployments, check for available security updates via your Microsoft support channels
  3. Review your build agent isolation practices — ensure agents are not running as privileged users and are network-segmented
  4. Audit pipeline inputs for unsanitized user-controlled parameters that may reach command execution surfaces
  5. Monitor MSRC for any additional advisory details or patches

Context: other Azure security updates this round

MSRC published this vulnerability alongside other Azure security updates in the same round, including:

  • CVE-2026-108456 — Azure AI Foundry SSRF privilege escalation
  • CVE-2026-83938 — Azure Kubernetes Configuration Service missing authentication

Acknowledgements

Jianyang Song of Microsoft reported this vulnerability. Microsoft recognizes the efforts of the security community in helping protect customers through coordinated vulnerability disclosure.

Sources