Code execution via undisclosed unsafe deserialization
Published Sep 12, 2023 · Updated Oct 30, 2025
Unsafe deserialization in Microsoft Identity Broker 1.0.0 through 1.6.0 allows local users to execute code through a crafted file. Microsoft identifies untrusted-data deserialization but has not published the affected parser, file format, or unsafe operation. Exploitation requires a user to open the attacker-supplied file and can expose or modify data, with no reported service interruption.
Summary
What happened
Unsafe deserialization in Microsoft Identity Broker 1.0.0 through 1.6.0 allows local users to execute code through a crafted file. Microsoft identifies untrusted-data deserialization but has not published the affected parser, file format, or unsafe operation. Exploitation requires a user to open the attacker-supplied file and can expose or modify data, with no reported service interruption.
The record
- CVE
- CVE-2023-36736
- Published
- Sep 12, 2023
- Updated
- Oct 30, 2025
- Vendor
- Microsoft
- Product
- Microsoft Identity Broker
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2023CVE publishedPublication date reported by the CVE source.
- Oct 30, 2025Record 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=1.0.0 <1.6.1
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