Loading vulnerability…
A critical information disclosure vulnerability in Microsoft Azure DevOps allowed an unauthenticated attacker to disclose sensitive information over the network. The issue is classified as CWE-200, Exposure of Sensitive Information to an Unauthorized Actor. Publicly available information does not identify the exact vulnerable Azure DevOps subcomponent, function, or exploitation mechanism, but the published CVSS v3.1 vector indicates network reachability, low attack complexity, no privileges required, no user interaction, and changed scope. The vulnerability affected the hosted Azure DevOps service and was remediated by Microsoft on the service side before public disclosure.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository is a standalone Python proof-of-concept/operational information-disclosure exploit for CVE-2026-42826 affecting Microsoft Azure DevOps Services and Azure DevOps Server 2022/2025. The main file is exploit.py, which implements a CLI-driven network exploit using only Python standard library modules. It sends HTTP(S) requests to Azure DevOps REST API endpoints, optionally authenticating with a PAT via Basic auth, and aggregates returned data into a structured report. Primary exploit capability is unauthorized reconnaissance and data extraction, not code execution. Based on the README, diagrams, tests, and visible exploit code, the tool supports: unauthenticated public-project discovery; enumeration of projects; pipeline enumeration and YAML extraction; variable group harvesting with masking of secret-marked values but capture of non-secret plaintext values; service connection enumeration exposing metadata such as Azure subscription IDs and tenant IDs; repository/file retrieval; build log retrieval; and regex-based scanning of collected content for sensitive artifacts such as AWS access keys, GitHub tokens, JWTs, email addresses, Azure subscription references, Kubernetes service connections, ARM token variable names, and PAT references. Repository structure: exploit.py is the main exploit entry point; detect.py is a companion detection/hardening checker rather than the exploit itself; test_exploit.py contains unit tests for URL construction, request handling, secret scanning, report generation, and public exposure logic; e2e_test.py spins up a local mock Azure DevOps API server on 127.0.0.1:18926 to validate end-to-end extraction behavior; README.md, USAGE.md, and DIAGRAM.md document attack flow, usage, and architecture; package.json only wraps Python commands for convenience. The exploit is credible and functional as an information-disclosure PoC. It is not framework-based, not fake, and not merely a detector. Maturity is OPERATIONAL because it includes working enumeration/reporting logic and a built-in data-scanning payload, but it does not deliver post-exploitation code execution. The most fingerprintable targets are Azure DevOps REST API paths under /_apis/projects, /_apis/pipelines, /_apis/distributedtask/variablegroups, /_apis/serviceendpoint/endpoints, /_apis/git/repositories, repository item retrieval, and build log endpoints.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical Azure DevOps information disclosure vulnerability in the cloud service that can expose CI/CD secrets and enable downstream compromise of pipelines, cloud service connections, repositories, and software supply chain.
An information disclosure vulnerability in Azure DevOps allowing unauthorized disclosure of information over a network.
An information disclosure vulnerability in Azure DevOps. Microsoft states it has already been fully mitigated on the service side, so users do not need to take action.
An Azure DevOps information disclosure vulnerability with a CVSS base score of 10.0.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.