CVE-2024-21409

Code execution via WPF use-after-free

Published Apr 9, 2024 · Updated May 3, 2025

Use-after-free in WPF in affected Microsoft .NET products allows local users to execute code after a user views an untrusted document. WPF retains or accesses an object after its lifetime ends, but Microsoft has not disclosed the affected function or object-lifetime sequence. Reachability is limited to WPF-based applications and requires user interaction; successful exploitation runs code in the user context.

CVSS severity7.3
High
EPSS probability2.51%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in WPF in affected Microsoft .NET products allows local users to execute code after a user views an untrusted document. WPF retains or accesses an object after its lifetime ends, but Microsoft has not disclosed the affected function or object-lifetime sequence. Reachability is limited to WPF-based applications and requires user interaction; successful exploitation runs code in the user context.

The record

CVE
CVE-2024-21409
Published
Apr 9, 2024
Updated
May 3, 2025
Vendor
Microsoft
Product
Microsoft .NET Framework 3.5 and 4.8.1
Classifications
CWE-416, T1203, T1204.002
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 9, 2024CVE publishedPublication date reported by the CVE source.
  2. May 3, 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.

  1. Affected versionversion=4.8.1 <4.8.9236.0

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Microsoft .NET Framework 3.5 and 4.8.1version=4.8.1 <4.8.9236.0
Microsoft · .NET 6.0version=6.0.0 <6.0.29
Microsoft · PowerShell 7.3version=7.3.0 <7.3.12
Microsoft · Microsoft .NET Framework 3.5 and 4.8version=4.8.0 <4.8.4718.0
Microsoft · Microsoft Visual Studio 2022 version 17.8version=17.8.0 <17.8.9
Microsoft · Microsoft Visual Studio 2022 version 17.6version=17.6.0 <17.6.14
Microsoft · Microsoft Visual Studio 2022 version 17.4version=17.4.0 <17.4.18
Microsoft · .NET 8.0version=8.0 <8.0.4
Microsoft · .NET 7.0version=7.0.0 <7.0.18
Microsoft · Microsoft .NET Framework 3.5 and 4.7.2version=4.7.0 <4.7.4092.0
Microsoft · Microsoft .NET Frameworkversion=4.7.0 <4.7.4092.0
Microsoft · PowerShell 7.2version=7.2.0 <7.2.19
Microsoft · PowerShell 7.4version=7.4.0 <7.4.2
Microsoft · Microsoft Visual Studio 2022 version 17.9version=17.0 <17.9.6
Microsoft · Microsoft .NET Framework 4.6.2version=4.7.0 <4.7.4092.0
Microsoft · Microsoft .NET Framework 4.8version=4.8.0 <4.8.4718.0

Published CVSS scores

7.3Microsoft CorporationCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
T1203Exploitation for Client Execution
T1204.002Malicious File

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