dbcve.org
Entra Provisioning ServiceApplication · Microsoft

CVE-2026-57100

HIGH · 8.8 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 7 weeks old

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 Microsoft Entra Provisioning Service (SyncFabric) allows an authorized attacker to elevate privileges over a network.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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

A server-side request forgery (SSRF) vulnerability in Microsoft Entra Provisioning Service (SyncFabric) allows an authenticated attacker to make the service perform unintended network requests, potentially reaching internal resources and elevating privileges over the network.

MitigationApply Microsoft security patches for Entra ID when available. Review and restrict network access controls for the provisioning service, and monitor for unusual outbound requests from Entra provisioning components.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm if Entra Provisioning Service is enabled
    Navigate to Microsoft Entra admin center > Identity > Applications > Enterprise applications. Look for any application with provisioning enabled, or check via Microsoft Graph API by querying the servicePrincipal object for provisioning configuration.
    Affected if The Entra Provisioning Service is configured and enabled for any application in the tenant
  2. Identify SyncFabric provisioning configuration
    Review the Enterprise application provisioning settings in the Entra admin center. Check for applications using the 'SyncFabric' or 'Provisioning' API type. Use Microsoft Graph to query the /beta/applications endpoint for provisioning configurations.
    Affected if Any application has provisioning configured to use the SyncFabric API endpoint
  3. Review provisioning service audit logs for unusual outbound requests
    In Entra admin center > Monitoring > Audit logs, filter by 'Provisioning Service' category. Look for entries with unusual target URLs, especially internal IP addresses, non-routable addresses (10.x.x.x, 192.168.x.x, 172.16-31.x.x), or custom API endpoints.
    Affected if Audit logs show outbound requests to unexpected internal or external destinations from the provisioning service
  4. Check network access from Entra provisioning components
    Review network security groups and firewall rules that allow outbound traffic from Microsoft Entra provisioning IPs. Examine Azure Log Analytics or network watcher logs for connections originating from provisioning service endpoints.
    Affected if The provisioning service has network paths to internal resources that should not be accessible

If Microsoft Entra Provisioning Service (SyncFabric) is enabled and configured in the tenant, the environment is affected by this SSRF vulnerability since all versions are vulnerable.

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 security patches for Entra ID when available. Review and restrict network access controls for the provisioning service, and monitor for unusual outbound requests from Entra provisioning components.

Fix this in Entra Provisioning Service Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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