CVE-2026-25265
8.8Qualcomm · Snapdragon
A privilege escalation vulnerability in Qualcomm Snapdragon software allows local users to gain elevated system privileges due to insecure temporary file handling.
Executive summary
A critical privilege escalation vulnerability in Qualcomm Snapdragon software allows local users to achieve full system control, necessitating immediate attention.
Vulnerability
The vulnerability, categorized as CWE-378, arises from insecure permissions during the creation of temporary files. An attacker with low-level local privileges can exploit this weak configuration to escalate their access level and potentially compromise the entire operating system.
Business impact
The CVSS score of 8.8 reflects the high risk associated with local privilege escalation, which can lead to total system compromise. Successful exploitation grants an attacker full control over the affected device, enabling unauthorized data access, the installation of malicious software, and complete disruption of business operations. This represents a significant security risk for organizations relying on Snapdragon-based Windows hardware.
Remediation
Immediate Action: Consult the Qualcomm security bulletin for June 2026 to identify and apply the necessary firmware or driver updates as soon as they become available.
Proactive Monitoring: Monitor system logs for unauthorized attempts to access or modify temporary directories and files, particularly those initiated by standard user accounts.
Compensating Controls: Implement strict file system permissions and endpoint security policies to limit the ability of low-privileged users to execute code or manipulate files in sensitive system directories.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Given the high severity and the potential for full system compromise, administrators should prioritize the identification of all affected Snapdragon-based Windows systems. Once Qualcomm releases the official patch or driver update, it must be deployed immediately to mitigate the risk of local privilege escalation.
More Qualcomm CVEs all →
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section