CVE-2026-33103
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 · uneditedImproper access control in Microsoft Dynamics 365 (on-premises) allows an authorized attacker to disclose information locally.
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 confidenceImproper access control in Microsoft Dynamics 365 (on-premises) allows an authorized user to bypass intended permission boundaries and disclose information they should not have access to. This is a vertical privilege escalation vulnerability where a user with legitimate but limited access can access higher-privilege information through the access control flaw.
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>= 9.0, < 9.1.44.15CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Dynamics 365 versionOpen Dynamics 365 Deployment Manager, right-click on the organization, and view the version information. Alternatively, run PowerShell cmdlet Get-CrmServer or check the Microsoft Dynamics 365 About page within the application.Affected if Installed version is 9.0.x through 9.1.44.14 (any version >= 9.0 but < 9.1.44.15)
-
Confirm deployment type is on-premisesVerify the Dynamics 365 deployment is hosted on-premises (not Dynamics 365 Online/Cloud). Check deployment manager or consult your infrastructure documentation.Affected if Deployment is Microsoft Dynamics 365 on-premises (the vulnerability does not apply to Dynamics 365 Online)
-
Identify non-admin user accountsReview user accounts in Dynamics 365 through Users area in Dynamics 365 or via PowerShell using Get-CrmUser to list all users and their security roles.Affected if There are authenticated users with standard/non-administrator security roles (exploitation requires a locally authenticated, authorized user with limited access)
-
Review role-based access control assignmentsExamine security roles and field-level security profiles assigned to standard users. Check which roles have access to sensitive entities like customer data, financial records, or admin configuration areas.Affected if Users with limited roles exist and could potentially view data beyond their assigned permissions (the vulnerability allows privilege escalation beyond intended role boundaries)
You are affected if running Microsoft Dynamics 365 on-premises version 9.0 through 9.1.44.14 and have authenticated users with limited permissions who could exploit improper authorization to access sensitive data beyond their intended role permissions.
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.
dbcve · scoped9.1.44.15
Apply the Microsoft security update for Dynamics 365 (on-premises) when available. Until then, enforce least-privilege access controls and monitor for anomalous data access patterns.
Dynamics 365 on-premises version 9.1.44.15 or later
- 1. Back up the Microsoft Dynamics 365 database and all customizations before starting the upgrade process
- 2. Review Microsoft Dynamics 365 version 9.1.44.15 release notes and prerequisites at docs.microsoft.com/dynamics365
- 3. Download the Dynamics 365 on-premises update 9.1.44.15 from the Microsoft Volume Licensing Service Center or Lifecycle Services
- 4. Apply the update in a non-production environment first to validate compatibility
- 5. Schedule a maintenance window and apply the update to production
- 6. Verify the version by checking About in Dynamics 365 Administration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33103 — 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-33103 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