Remote code execution via SAPI use-after-free
Published Oct 8, 2024 · Updated Aug 19, 2026
Use-after-free in Microsoft SAPI on affected Windows releases allows remote attackers to execute code after user interaction. Microsoft identifies freed-object reuse in the SAPI component but has not disclosed the responsible function, object lifetime error, or crafted input format. Successful exploitation requires a user action and runs code in the compromised user's context, permitting data access, modification, and service interruption.
Summary
What happened
Use-after-free in Microsoft SAPI on affected Windows releases allows remote attackers to execute code after user interaction. Microsoft identifies freed-object reuse in the SAPI component but has not disclosed the responsible function, object lifetime error, or crafted input format. Successful exploitation requires a user action and runs code in the compromised user's context, permitting data access, modification, and service interruption.
The record
- CVE
- CVE-2024-43574
- Published
- Oct 8, 2024
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Windows 11, version 24H2
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=10.0.26100.0 <10.0.26100.2033
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.
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