CVE-2025-47319VulnerabilityPublished 18 Dec 2025

CVE-2025-47319: Qualcomm Snapdragon · Exposure of Sensitive System Information to an Unauthorized Control Sphere

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 6.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.7Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.09% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor Qualcomm and device vendors for official patches or firmware updates addressing CVE-2025-47319 and apply them promptly once available. 2. Enforce strict access control policies on devices using affected Snapdragon platforms to limit local privilege escalation opportunities, including restricting administrative or root access to trusted personnel only. 3. Implement robust endpoint security solutions capable of detecting and preventing privilege escalation and suspicious local activity on mobile and automotive devices. 4. For enterprise environments, employ Mobile Device Management (MDM) solutions to enforce security policies, including disabling unnecessary debug or developer modes that could facilitate exploitation. 5. Conduct regular security audits and vulnerability assessments on devices incorporating affected Qualcomm components, focusing on privilege boundaries and TEE interactions. 6. Educate users and administrators about the risks of installing untrusted applications or software that could gain elevated privileges. 7. For automotive systems, collaborate with OEMs and suppliers to ensure secure firmware updates and integrity verification mechanisms are in place to prevent unauthorized modifications. 8. Consider network segmentation and isolation strategies for critical IoT and automotive devices to limit lateral movement if a device is compromised.

Description

Information disclosure while exposing internal TA-to-TA communication APIs to HLOS

Impact

For European organizations, the impact of CVE-2025-47319 is primarily on confidentiality of sensitive information processed within devices using affected Qualcomm Snapdragon components. This includes smartphones, tablets, automotive infotainment and telematics systems, IoT devices, and potentially enterprise mobile endpoints. Leakage of cryptographic keys or authentication credentials could lead to further compromise of user data, unauthorized access to corporate resources, or bypassing of device security features. Automotive systems are particularly sensitive as they may control safety-critical functions; exposure of internal communications could undermine trust in vehicle security. The vulnerability does not directly affect availability or integrity, but the confidentiality breach could facilitate secondary attacks. Organizations relying on mobile device management (MDM) or automotive telematics with Snapdragon hardware should be aware of the risk of local privilege escalation leading to sensitive data exposure. Given the widespread deployment of Snapdragon chipsets in Europe, the potential attack surface is large. However, the requirement for high privilege local access limits remote exploitation risk, reducing immediate threat from external attackers but increasing concern over insider threats or malware with elevated privileges.

CWE-497Exposure of Sensitive System Information to an Unauthorized Control Sphere (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
Architecture and Design · Implementation
Production applications should never use methods that generate internal details such as stack traces and error messages unless that information is directly committed to a log that is not viewable by the end user.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.3.2 (opens in a new tab)
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
Attack patterns
Web Application Fingerprinting (opens in a new tab)
System Location Discovery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/december-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 25 Dec 2025, 07:04 UTC

WeaknessesCWE-497

Technical details

References

Community reviews

Related threats