Microsoft Azure DevOps msazure insufficiently protected credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Microsoft Azure DevOps. Affected by this issue is some unknown functionality of the component msazure. Performing a manipulation results in insufficiently protected credentials. This vulnerability is identified as CVE-2026-23658. The attack can be initiated remotely. There is not any exploit available. This product operates as a managed service, which prevents users from maintaining vulnerability countermeasures themselves.
Details
A vulnerability classified as problematic has been found in Microsoft Azure DevOps (affected version unknown). This affects an unknown functionality of the component msazure. The manipulation with an unknown input leads to a insufficiently protected credentials vulnerability. CWE is classifying the issue as CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. This is going to have an impact on confidentiality. The summary by CVE is:
Insufficiently protected credentials in Azure DevOps allows an unauthorized attacker to elevate privileges over a network.
It is possible to read the advisory at msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2026-23658 since 01/14/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/24/2026). The attack technique deployed by this issue is T1552 according to MITRE ATT&CK.
This product is available as a managed service. Users are not able to maintain vulnerability countermeasures themselves.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
License
Managed Service
- yes
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.6
CNA Vector (microsoft): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Insufficiently protected credentialsCWE: CWE-522
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Status: 🔍0-Day Time: 🔒
Timeline
01/14/2026 CVE reserved03/20/2026 Advisory disclosed
03/20/2026 VulDB entry created
03/24/2026 VulDB entry last update
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2026-23658 (🔒)
GCVE (CVE): GCVE-0-2026-23658
GCVE (VulDB): GCVE-100-351891
Entry
Created: 03/20/2026 07:55Updated: 03/24/2026 08:57
Changes: 03/20/2026 07:55 (63), 03/24/2026 08:57 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.