Privilege escalation via DLL hijacking
Published May 15, 2026 · Updated May 15, 2026
DLL hijacking in AMD Cleanup Utility allows local users to execute arbitrary code with elevated privileges after user interaction. AMD identifies the affected locus only as the Cleanup Utility and has not disclosed the DLL name or unsafe search-path operation that loads attacker-controlled code. Exploitation requires existing low privileges and passive user interaction, and the resulting process can compromise confidentiality, integrity, and availability.
Summary
What happened
DLL hijacking in AMD Cleanup Utility allows local users to execute arbitrary code with elevated privileges after user interaction. AMD identifies the affected locus only as the Cleanup Utility and has not disclosed the DLL name or unsafe search-path operation that loads attacker-controlled code. Exploitation requires existing low privileges and passive user interaction, and the resulting process can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2024-36333
- Published
- May 15, 2026
- Updated
- May 15, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD Radeon RX Vega Series Graphics Cards
- Classifications
- CWE-427, T1574.002
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 15, 2026CVE publishedPublication date reported by the CVE source.
- May 15, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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