On this page (8 sections)
CVE-2026-109467 is a critical vulnerability in Azure DevOps. According to the NVD record, improper authentication in Azure DevOps allows an authorized attacker to execute code over a network. The record was published on 2026-11-10 and carries a CVSS score of 9.9.
If your team uses Azure DevOps for source code, pipelines or releases, you should read the vendor entry and plan a response. Only one independent publisher covers this story so far, and the public record is short, so this article separates what is confirmed from what is not.
What the record says
The entire public description is one sentence: improper authentication in Azure DevOps allows an authorized attacker to execute code over a network. The vendor reference is the Microsoft Security Response Center entry. The CVE record has no CISA Known Exploited Vulnerabilities entry. That is not the same as confirmation that the flaw is unexploited, and the research does not say either way.
Several details are not available in the sources we have: which Azure DevOps components or versions are affected, whether the issue applies to the cloud service, to self-hosted Azure DevOps Server, or both, what the fix is, and how the flaw is triggered. Treat any claim beyond the description above as unconfirmed until Microsoft's advisory says otherwise.
What the weakness class means
CWE-287 covers cases where software does not properly prove that a caller is who they claim to be, or that they are allowed to perform an action. In a development platform, that can mean a request is accepted with weaker proof of identity or permission than intended.
The phrase authorized attacker matters. It suggests the attacker already holds some valid access, such as an account in the organization, and the flaw lets them go further than that access should allow. The record does not say how much access is needed. A 9.9 score is consistent with a flaw that can affect resources beyond the attacker's own permissions, but the research does not give the CVSS vector, so we cannot confirm scope or privilege requirements.
Why Azure DevOps flaws deserve attention
Build and release systems hold a lot of trust. They typically store or can reach source code, secrets, package feeds, signing steps and deployment credentials for production websites and cloud environments. Code execution in that environment can be a stepping stone to everything it deploys. This is general context about CI/CD systems, not a finding from the advisory.
Who is realistically exposed
- Organizations using Azure DevOps, especially those with many contributors, contractors or external guest accounts, since the attacker is described as authorized.
- Teams running build agents or service connections with broad rights to production, cloud subscriptions or hosting accounts.
- Agencies that manage client repositories and deployments from a shared organization.
- Anyone running a self-hosted Azure DevOps deployment, until Microsoft confirms whether it is affected.
How to check your exposure
Start with the vendor entry, because it is the authoritative source for affected products and fixes.
- Open the Microsoft advisory for CVE-2026-109467 and note the affected products and any listed update.
- Inventory where you use Azure DevOps: hosted organizations, any self-hosted servers, and which projects deploy to production.
- If you self-host, record the installed version and compare it with the fixed version in the advisory once it is listed.
- List who has access: members, guests, service accounts and personal access tokens with write or pipeline permissions.
What to do now
- Read the Microsoft advisory and apply any update or mitigation it lists, starting with self-hosted servers.
- Review organization membership and remove accounts, guests and tokens that are no longer needed.
- Apply least privilege: limit who can edit pipelines, create agents or manage service connections.
- Reduce the reach of pipeline identities so a compromised build cannot touch production by default.
- Rotate secrets and tokens stored in or reachable from pipelines if you see anything suspicious.
- Review recent audit logs for unexpected pipeline changes, new service connections or unusual token use.
- Check Microsoft's advisory again for updates to this CVE, since details may change as more information is published.
Detection and monitoring
Because the technical details are not public in our sources, there are no reliable indicators of compromise to share. Focus on behavior you can verify in your own environment: pipeline definitions that changed without a matching pull request, new or modified service connections, agents registered from unexpected hosts, and builds that make outbound connections you do not recognize.
Sites that deploy through Azure DevOps should also watch what gets published. Monitoring for unexpected changes to certificates, DNS records and response headers can help you notice a bad deployment sooner, as can Webforta Monitor. This does not detect the vulnerability itself. The free security headers checker is a quick way to compare your live headers before and after a release.
If you suspect a pipeline was abused to ship malicious code, follow the steps in Website hacked: what to do.
Timeline
| Date | Event |
|---|---|
| 2026-11-10 | CVE-2026-109467 published in NVD with CVSS 9.9 and CWE-287 |
| 2026-11-10 | Microsoft advisory referenced by the CVE record |
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
