dbcve.org
Azure Devops ServerOperating system · Microsoft

CVE-2026-21512

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 2022.2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Server-side request forgery (ssrf) in Azure DevOps Server allows an authorized attacker to perform spoofing 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 a Server-Side Request Forgery (SSRF) vulnerability in Azure DevOps Server. An authorized attacker can exploit the server to make network requests to arbitrary locations, potentially accessing internal services, scanning intranet resources, or exfiltrating data by leveraging the server's trusted network position.

MitigationApply the vendor patch when released by Microsoft. Until then, implement network segmentation to restrict Azure DevOps Server's outbound connectivity to only necessary endpoints, and monitor for unusual outbound requests.

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 Devops ServerOperating system
Affected:< 2022.2.0= 2022.2.0

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm Azure DevOps Server installation
    Locate the Azure DevOps Server installation directory, typically at C:\Program Files\Azure DevOps Server 2020 or similar path depending on version, or check Programs and Features in Control Panel for 'Azure DevOps Server' entry
    Affected if Azure DevOps Server is installed on the system
  2. Identify installed Azure DevOps Server version
    Open Azure DevOps Server Administration Console, or run 'TFSConfig /version' from the installation bin directory, or check the installed programs list for the exact version number
    Affected if The installed version is less than 2022.2.0 or exactly 2022.2.0
  3. Check Azure DevOps Server web portal accessibility
    Access the Azure DevOps Server web interface at the configured base URL (e.g., http://servername:8080/tfs) and verify the server is reachable over the network
    Affected if The Azure DevOps Server web portal is accessible and the version is vulnerable
  4. Review Azure DevOps Server network configuration
    Check Azure DevOps Server Administration Console under 'Web Service URLs' and 'ServerURL' settings to confirm the server is configured with network-accessible endpoints
    Affected if The server has outbound network capability enabled and is on a vulnerable version

If the installed Azure DevOps Server version is any release prior to 2022.2.0 or exactly 2022.2.0, the environment is affected by this SSRF vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2022.2.0 or later
Fixed in 2022.2.0
Interim mitigation

Apply the vendor patch when released by Microsoft. Until then, implement network segmentation to restrict Azure DevOps Server's outbound connectivity to only necessary endpoints, and monitor for unusual outbound requests.

Recommended fix Moderate confidence

Azure DevOps Server 2022.2.1 or later (any version above 2022.2.0)

  1. 1. Identify the current Azure DevOps Server version by navigating to the Azure DevOps Administration Console or checking the installed programs.
  2. 2. Confirm the installed version is either below 2022.2.0 or exactly 2022.2.0.
  3. 3. Before upgrading, perform a complete backup of the Azure DevOps Server databases and configuration, following Microsoft's documented backup procedures.
  4. 4. Download the latest Azure DevOps Server update from the official Microsoft Visual Studio portal or Microsoft Download Center.
  5. 5. Run the installer on the Azure DevOps Server application tier, following the upgrade wizard prompts.
  6. 6. After upgrade completes, verify all Azure DevOps services are running correctly and test core functionality.
  7. 7. Confirm the upgraded version is greater than 2022.2.0 to ensure the SSRF vulnerability (CVE-2026-21512) is patched.
Caveat Review Azure DevOps Server release notes for any breaking changes between 2022.2.x versions; upgrades between minor versions typically have minimal compatibility impact but validate extension compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Azure Devops Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21512 — 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-2026-21512 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