CVE-2026-26138
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 · uneditedServer-side request forgery (ssrf) in Microsoft Purview 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 confidenceServer-side request forgery (SSRF) in Microsoft Purview enables an unauthorized attacker to make the service perform network requests on their behalf. This can allow access to internal resources, potentially cloud metadata services, and privilege escalation across the network infrastructure.
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 dataall versionsCVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Microsoft Purview deploymentCheck your Microsoft 365 admin center or Azure portal to verify if Microsoft Purview is enabled in your tenant. Look under Purview solutions or the compliance manager.Affected if Microsoft Purview is active in the tenant - all versions are affected per vendor scope
-
Review Purview audit logs for outbound requestsAccess the Microsoft Purview compliance portal audit logs. Search for activities involving data sources or external connections initiated by Purview connectors.Affected if Unusual outbound connections appear from Purview to unexpected internal or external destinations
-
Monitor for metadata service access attemptsCheck network logs or cloud infrastructure logs for requests from Purview IPs to cloud metadata endpoints (169.254.169.254 for Azure/AWS, metadata.google.internal for GCP).Affected if Purview generates requests to cloud metadata IP addresses, indicating potential SSRF exploitation
-
Inspect internal network access patternsReview network flow logs, firewall logs, or Azure Network Watcher for outbound traffic originating from Purview-managed resources to RFC1918 private ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).Affected if Purview makes outbound requests to internal private network addresses that were not configured
-
Analyze admin activity logs for unauthorized data source additionsExamine Microsoft Purview Data Map audit logs for any new data source connections or scans initiated without corresponding admin action.Affected if New data sources appear in the Purview Data Map that were not intentionally created by your administrators
If Microsoft Purview is in use and anomalous outbound network requests to internal resources or cloud metadata services are observed in logs, the environment is likely affected by this SSRF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataSince this is a Microsoft service vulnerability, customers must await Microsoft's official patch. In the interim, restrict outbound network access from Purview-managed resources and monitor for unusual internal network requests.
- Consultation8.0 h
- Testing4.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,672.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26138 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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