CVE-2025-47348
Qualcomm Aqt1000 Firmware
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-47348 is a high-severity Use of Uninitialized Variable (CWE-457) vulnerability in Qualcomm Aqt1000 Firmware. Its CVSS base score is 7.8 (High).
Operationally, ranked at the 0.1th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-47348 is a memory corruption vulnerability, classified under CWE-457 (Use After Free), that occurs while processing identity credential operations in the trusted application. It affects Qualcomm products, as detailed in their security bulletin. The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and was published on 2026-01-07T12:17:04.457.
A local attacker with low privileges can exploit this vulnerability through low-complexity means without requiring user interaction. Successful exploitation enables high-impact consequences across confidentiality, integrity, and availability, potentially leading to arbitrary code execution or disruption within the trusted application context.
Qualcomm's January 2026 security bulletin provides further details on the vulnerability, available at https://docs.qualcomm.com/product/publicresources/securitybulletin/january-2026-bulletin.html, including information on affected products and recommended mitigations or patches.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-1252
Vulnerability Data
Memory corruption while processing identity credential operations in the trusted application.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
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 catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
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.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Secure development life cycle mandates practices that reduce uninitialized-variable defects.
Application security requirements can specify initialization rules, but the control itself does not directly address the weakness.
Secure coding explicitly requires variable initialization and static-analysis checks.
Secure architecture principles encourage defensive coding that can mitigate uninitialized variables.