dbcve.org
Azure DevopsApplication · Microsoft

CVE-2025-47158

CRITICAL · 9.0 CVSS v3.1 Published 2025-07-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication bypass by assumed-immutable data in Azure DevOps allows an unauthorized attacker to elevate privileges over a network.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an authentication bypass vulnerability in Azure DevOps where certain data that was assumed to be immutable can be manipulated, allowing an unauthenticated attacker to elevate privileges to higher access levels over a network.

MitigationApply Microsoft-provided patches for Azure DevOps when released; review Azure DevOps audit logs for signs of exploitation; implement least-privilege access controls as a defensive measure until patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Azure DevopsApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Azure DevOps deployment type
    Determine if your organization uses Azure DevOps Services (cloud) or Azure DevOps Server (on-premises). This matters because patch availability and application differ between deployment types.
    Affected if Running any version of Azure DevOps Server on-premises or any tenant of Azure DevOps Services.
  2. Check currently installed Azure DevOps Server version
    On the Azure DevOps Server application tier machine, open Azure DevOps Administration Console and view the version number displayed on the Server Information tab. For Azure DevOps Services, this information is available in the organization settings under Organization overview.
    Affected if Any version is installed, since the advisory states all versions are affected.
  3. Review Azure DevOps audit logs for authentication anomalies
    Navigate to Azure DevOps organization settings, select Audit log, and examine entries around the time window of potential exploitation. Look for successful actions performed in short succession, especially privilege escalation actions like adding users to elevated security groups, modifying project permissions, or accessing resources outside normal patterns.
    Affected if Audit logs show unauthenticated or unexpected authenticated actions that correlate with privilege escalation activities.
  4. Examine security group membership changes
    In Azure DevOps organization settings, go to Security and review recent changes to security groups, especially Administrator groups, Project Collection Administrator groups, or any group granting elevated access. Check who added members and whether that activity aligns with expected administrative actions.
    Affected if Unexpected members added to privileged security groups without legitimate administrative approval.
  5. Inspect API and service hook activity logs
    In Azure DevOps, review API call logs and service hook delivery history for patterns indicating unauthorized data manipulation, particularly calls that modified user permissions, access control entries, or security settings without proper authentication context.
    Affected if API calls or service hook executions successfully modified security-relevant data without valid authentication credentials.

A defender is affected if they run any version of Azure DevOps and their audit logs or security configurations show evidence of unauthorized privilege escalation or authentication bypass attempts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft-provided patches for Azure DevOps when released; review Azure DevOps audit logs for signs of exploitation; implement least-privilege access controls as a defensive measure until patch is available.

Fix this in Azure Devops Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47158 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data