Local code execution via DLL search-path hijacking
Published Jul 22, 2025 · Updated Feb 26, 2026
Uncontrolled DLL search paths in Arm Development Studio before 2025 allow local users to execute code in the current user's context. Arm has not disclosed the executable, library name, or searched directory responsible for loading an attacker-controlled DLL. Exploitation requires a crafted DLL in a searched location, and the resulting code inherits the application's user privileges.
Summary
What happened
Uncontrolled DLL search paths in Arm Development Studio before 2025 allow local users to execute code in the current user's context. Arm has not disclosed the executable, library name, or searched directory responsible for loading an attacker-controlled DLL. Exploitation requires a crafted DLL in a searched location, and the resulting code inherits the application's user privileges.
The record
- CVE
- CVE-2025-7427
- Published
- Jul 22, 2025
- Updated
- Feb 26, 2026
- Vendor
- Arm
- Product
- Arm Development Studio
- Classifications
- CWE-427, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=0 <2025
What conditions does exploitation require?
What is affected?
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