Security readout for executives and security teams
Plain-English summary
An authenticated attacker could cause Azure DevOps Server to make unintended network requests, potentially exposing information accessible from the server. The supplied title calls this cross-site scripting, but the description and CWE classify it as server-side request forgery. Treat the technical classification as SSRF while confirming details with Microsoft.
Executive priority
Prioritize remediation in the normal security-update cycle, accelerating internet-facing or highly connected instances. Although rated medium, possible high confidentiality impact warrants prompt inventory and patch verification. There is no supplied evidence of active exploitation.
Technical view
CVE-2026-21512 is described as SSRF (CWE-918) affecting Azure DevOps Server 2022 version 20230131.0. It is remotely reachable, requires low privileges, needs no user interaction, and may cause high confidentiality impact without stated integrity or availability impact. CVSS 3.1 is 6.5.
Likely exposure
Exposure is supported only for Azure DevOps Server 2022 version 20230131.0. Risk is greater where authenticated, low-privilege users can reach the service and the server can access sensitive internal resources. The bundle does not establish whether other versions are affected.
Exploitation context
The supplied sources do not confirm active exploitation, and the CVE is not listed as KEV in the bundle. The CVSS exploit-maturity metric is unproven. Successful abuse requires an authorized attacker with low privileges; no user interaction is indicated.
Researcher notes
The bundle contains a material classification inconsistency: its title says cross-site scripting, while its description, CWE-918, and confidentiality-focused vector indicate SSRF. The stated outcome is information exposure; integrity and availability impacts are scored none. No exploit method or specific fixed version is provided.
Mitigation direction
- Identify Azure DevOps Server 2022 instances and confirm their installed versions.
- Review Microsoft’s advisory and apply its published security update through approved change management.
- Restrict unnecessary low-privilege access until remediation is verified.
- Limit server egress and access to sensitive internal services where operationally feasible.
Validation and detection
- Verify whether any instance runs affected version 20230131.0.
- Confirm Microsoft’s applicable update is installed on every affected instance.
- Review outbound request logs for unusual internal or external destinations.
- Retest access controls and required service functionality after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-21512 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C2.83.6microsoftVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Azure DevOps Server Cross-Site Scripting VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.