Code execution via unsafe XPS type instantiation
Published Dec 13, 2022 · Updated May 27, 2026
Code injection in Microsoft .NET WPF XPS parsing allows remote attackers to execute arbitrary code when a user opens a crafted XPS file. RestrictiveXamlXmlReader relies on a deny list that permits unexpected XAML types to be instantiated, enabling an object gadget chain during document parsing. The affected path is limited to Windows WinForms or WPF applications; applications that do not use either framework and non-Windows targets are unaffected.
Summary
What happened
Code injection in Microsoft .NET WPF XPS parsing allows remote attackers to execute arbitrary code when a user opens a crafted XPS file. RestrictiveXamlXmlReader relies on a deny list that permits unexpected XAML types to be instantiated, enabling an object gadget chain during document parsing. The affected path is limited to Windows WinForms or WPF applications; applications that do not use either framework and non-Windows targets are unaffected.
The record
- CVE
- CVE-2022-41089
- Published
- Dec 13, 2022
- Updated
- May 27, 2026
- Vendor
- Microsoft
- Product
- Microsoft .NET Framework 3.5 and 4.8.1
- Classifications
- CWE-94, T1566.001, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 13, 2022CVE publishedPublication date reported by the CVE source.
- May 27, 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=4.8.1 <09115.01
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