Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure developer to malicious origin
-
ExploitVictim runs Azure DevOps CLI command
-
ExecutionExtension fails origin validation
-
ImpactSensitive data disclosed to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Exploitation requires a user to actively invoke the vulnerable Azure DevOps CLI Extension (version 1.0.6, fixed in 1.0.7) or Azure CLI against an origin that the attacker controls or can influence, triggering the origin validation error (CWE-346) that leaks high-confidentiality data. The key LIMITING factors are: required user interaction (CVSS UI:R) - the victim must run a CLI command, so there is no silent remote server-side exploitation; the affected surface is client-side developer/CI tooling rather than the hosted Azure DevOps service; and systems patched to Azure DevOps CLI Extension 1.0.7 or later are not vulnerable. No attacker authentication is needed (PR:N). |
| Impact | This is a moderate-severity information disclosure flaw (CVSS 6.5) in the Azure DevOps CLI extension / Azure CLI, not the Azure DevOps web service - an important distinction, since the affected component is developer/CI-side tooling rather than a server-side endpoint. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) indicates a network-reachable, low-complexity, unauthenticated attack that nonetheless requires user interaction (UI:R) and yields high confidentiality impact with no integrity or availability effect. All exploitation signals point AWAY from urgent priority: CISA SSVC rates Exploitation as 'none', Automatable 'no', and Technical Impact only 'partial'; there is no CISA KEV listing and no public exploit identified. EPSS is not provided in the input, so probabilistic exploitation likelihood cannot be quantified. The combination of PR:N but UI:R is notable - although no privileges are needed, the requirement that a user actively run a CLI command (likely against an attacker-influenced origin, consistent with CWE-346 origin validation error) substantially limits opportunistic mass exploitation. Overall this reads as a genuine but non-urgent patch-in-normal-cycle issue rather than a high-real-risk emergency. |
| Exploit ScenarioDerived | An attacker lures a developer into running an Azure DevOps CLI command that interacts with an attacker-controlled or attacker-influenced endpoint; because the extension fails to properly validate the response origin (CWE-346), sensitive information such as tokens or project data is disclosed to the wrong party. The attack requires the victim to take an action (UI:R) but no authentication on the attacker's part. No public proof-of-concept exploit has been identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Information disclosure in the Azure DevOps CLI Extension (1.0.6) and Azure CLI lets an attacker who controls or can influence the origin a CLI command is directed at expose high-confidentiality data from the developer or CI environment where the command runs. The attack is not silent or server-side: it requires the victim to actively invoke the affected CLI tooling against the attacker-influenced origin (CVSS UI:R), and no attacker authentication is needed (PR:N). The vulnerable surface is client-side developer/CI tooling rather than the hosted Azure DevOps service, and version 1.0.7 is fixed. No public exploit code and no confirmed active exploitation were identified at time of analysis, and CISA's SSVC assessment rates exploitation as none and automatable as no with partial technical impact.
RemediationAI
Vendor-released patch: Azure DevOps CLI Extension 1.0.7 (Microsoft MSRC advisory https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69877). Upgrade the azure-devops extension on every developer workstation and CI runner to 1.0.7 or later using the standard extension update mechanism (for example, az extension update --name azure-devops), and verify the installed version afterwards since pipelines can silently pin older extension versions in cached images. Where immediate upgrade is not possible, reduce exposure by preventing CLI invocations against untrusted or third-party-controlled origins - restrict scripts and pipeline steps to hardcoded, verified Azure DevOps endpoint hostnames, and block CI jobs from resolving or dialing arbitrary external hosts. Organizations should also audit configuration and logs for CLI commands pointed at unexpected endpoints, and treat tokens or credentials that may have been transmitted to an unverified origin as potentially exposed and rotate them; the trade-off of this compensating control is reduced flexibility for users who legitimately work against multiple or proxy endpoints. Disabling the extension entirely removes the risk but also removes Azure DevOps CLI functionality from affected machines.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-346 (Origin Validation Error), a class of defect in which a component fails to correctly verify the origin of a request, message, or resource before trusting it. Origin checks are most familiar from browser security models (CORS, postMessage, WebSocket handshakes), but the same logic applies to CLI tooling that talks to service endpoints: if the extension does not rigorously validate the scheme/host/origin it is communicating with, an attacker-controlled or attacker-influenced endpoint can be treated as legitimate and receive data that should only go to the trusted Azure DevOps origin. Because the affected component is the Azure DevOps CLI extension (EUVD lists Azure DevOps CLI Extension 1.0.6 and a corresponding Azure CLI range, both fixed in 1.0.7), the exposure is on the client side - the developer workstation or CI runner - where credentials, tokens, and command payloads may be transmitted. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N describes a network-reachable, low-complexity condition that needs a user to run the tool, produces no integrity or availability impact, but yields high confidentiality loss with scope unchanged (no CPE strings were supplied in the feed; version data comes from the ENISA EUVD entry).
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-reachable, low-complexity, unauthenticated (PR:N) but needs the victim to run a CLI command (UI:R); impact is confidentiality-only information disclosure, so I:N/A:N.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Origin validation error in Azure DevOps allows an unauthorized attacker to disclose information over a network.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-99597
GHSA-pvrq-8c6v-2w34
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB