CVE-2026-25265
Qualcomm Software Center 1.17.1 … 1.26.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25265 is a high-severity Creation of Temporary File With Insecure Permissions (CWE-378) vulnerability in Qualcomm Software Center. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-84348
Vulnerability Data
Privilege escalation due to weak configuration while temporary file handling.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 enforces access authorizations on system resources including files, structurally stopping insecure temporary file permissions from being exploitable.
AC-6 limits privileges granted to processes creating or accessing temporary files, reducing blast radius of insecure permissions.
SC-4 directly stops unauthorized information transfer through shared resources such as temporary files created with weak permissions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper temporary-file creation and permission handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure SDLC mandates secure handling of temporary files and permissions.
Application security requirements include secure creation and permissioning of temporary files.
Secure architecture principles require least-privilege file creation and access controls.
Secure coding standards directly prohibit insecure temporary file creation and permissions.
Security testing can detect insecure temporary files but does not prevent their creation.
Information access restriction can limit exposure but does not address file creation itself.