Authenticated code execution via untrusted deserialization
Published Sep 8, 2026 · Updated Sep 9, 2026
Deserialization of untrusted data in Microsoft Dynamics 365 on-premises before 9.1.0046.0006 allows remote authenticated users to execute code. Microsoft identifies unsafe deserialization but has not disclosed the receiving endpoint, serialized format, or code path that processes the attacker-controlled data. A valid low-privilege account and network access are required; successful exploitation executes code within the affected server's security context.
Summary
What happened
Deserialization of untrusted data in Microsoft Dynamics 365 on-premises before 9.1.0046.0006 allows remote authenticated users to execute code. Microsoft identifies unsafe deserialization but has not disclosed the receiving endpoint, serialized format, or code path that processes the attacker-controlled data. A valid low-privilege account and network access are required; successful exploitation executes code within the affected server's security context.
The record
- CVE
- CVE-2026-65772
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Microsoft Dynamics 365 (on-premises) version 9.1
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9.0 <9.1.0046.0006
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo