Azure DevOps Server Pipeline Remote Code Execution
CVE-2026-109467 is an improper authentication vulnerability in Microsoft Azure DevOps and Azure DevOps Server 2025. An authenticated attacker with Project Reader access can send a specially crafted network request to trigger pipeline execution that the identity is not authorized to initiate, potentially enabling code execution on pipeline agents without additional user interaction. Azure DevOps Server 2025 installations before Patch 9 are affected; the hosted Azure DevOps service has been fixed. The specific vulnerable endpoint, request format, and underlying authentication mechanism have not been publicly disclosed.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can compromise pipeline agents and resources accessible to their execution context. Depending on configuration, code executing within a pipeline may access resources through job access tokens, agent service accounts, and authorized service connections, potentially affecting build, deployment, and cloud infrastructure beyond the initiating user's permissions. The CVSS v3.1 assessment is 9.9, with changed scope, high confidentiality and integrity impacts, and low availability impact.
If you can’t patch tonight, do this now.
No vulnerability-specific interim workaround is documented. Complementary impact-reduction measures include running agents with least-privileged service accounts, separating agent pools by project, limiting service-connection permissions, and authorizing service connections per pipeline. Microsoft-hosted agents can provide a clean virtual machine for each run where feasible. These measures are not established as preventing exploitation and do not replace Patch 9.
Patch, then assume compromise.
Install Azure DevOps Server 2025 Patch 9 on affected self-hosted installations, including base installations and Patch 1 through Patch 8. Patch 9 was released on October 13, 2026, and is the identified fixed release. Verify the patch package against Microsoft's published SHA256 value before installation. Microsoft has already fixed the hosted Azure DevOps service; hosted customers have no patch to install.
No public exploits tracked yet. Mallory keeps watching.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.