VulnerabilityPublished 2 Feb 2026Updated 26 Feb 2026

CVE-2025-47366: Qualcomm Snapdragon · Exposed Dangerous Method or Function

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score

7.1High

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 2 Feb 2026
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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
Qualcomm, Inc.Snapdragon	Affected AR8035 – WSA8845 67 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2025-47366, organizations and device manufacturers should prioritize the following actions: 1) Apply vendor-supplied patches or firmware updates as soon as they become available to address the outdated Trusted Zone code. 2) Implement strict input validation and sanitization in the HLOS to prevent malformed or malicious inputs from reaching the Trusted Zone. 3) Restrict local access to devices and enforce least privilege principles to minimize the risk of attackers gaining the required local privileges. 4) Employ runtime integrity checks and monitoring within the Trusted Zone to detect anomalous behavior or unauthorized method invocations. 5) Use hardware-backed security features and secure boot mechanisms to ensure the integrity of the Trusted Zone environment. 6) For enterprise deployments, enforce device management policies that limit installation of untrusted applications and monitor for suspicious local activity. 7) Collaborate with Qualcomm and device vendors to receive timely vulnerability disclosures and updates. 8) Conduct regular security assessments and penetration testing focusing on local privilege escalation and cryptographic module security. These targeted measures go beyond generic advice by focusing on the unique Trusted Zone context and local privilege exploitation vector.

Description

Cryptographic issue when a Trusted Zone with outdated code is triggered by a HLOS providing incorrect input.

Impact

The impact of CVE-2025-47366 is significant for organizations and end-users relying on affected Qualcomm Snapdragon platforms. Successful exploitation can lead to unauthorized disclosure of sensitive cryptographic keys or data, undermining device security, secure communications, and trusted operations. This can facilitate further attacks such as privilege escalation, data tampering, or bypassing security controls. Given the widespread use of Snapdragon chipsets in smartphones, tablets, automotive systems, wearables, and IoT devices, the vulnerability poses a risk to personal privacy, corporate data security, and critical infrastructure relying on these platforms. Attackers with local access could leverage this flaw to compromise device integrity and confidentiality without alerting users. The absence of user interaction lowers the barrier for exploitation in compromised or multi-user environments. Although availability is not impacted, the breach of confidentiality and integrity can have cascading effects on trust and operational security. Enterprises deploying Snapdragon-based devices in sensitive environments, including government, finance, healthcare, and automotive sectors, face elevated risks of data breaches and operational disruption.

CWE-749Exposed Dangerous Method or Function (opens in a new tab)
Base weaknessLikelihood of exploit: LowOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
Architecture and Design
If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
Architecture and Design · Implementation · Attack Surface Reduction
Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users; restricted to a small set of privileged users; prevented from being directly accessible at all
OWASP Cheat Sheets
Third Party Javascript Management (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V14.5.1 (opens in a new tab)
V10.1.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
Attack patterns
WebView Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 07:28 UTC

WeaknessesCWE-749

Technical details

References

Community reviews

Related threats