Skip to main content
VulnerabilityPublished

CVE-2025-47369: Qualcomm Snapdragon · Information Exposure

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.07% 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:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
Qualcomm, Inc.SnapdragonAffected
  • AR8035 – WSA8845
73 affected builds
Fixed in–

AI-suggested

  1. Restrict access to IOCTL interfaces that provide session ID information to only trusted and authenticated processes, using strict access control mechanisms at the OS level.
  2. Employ application whitelisting and privilege management to minimize the risk of local privilege escalation that could enable exploitation of this vulnerability.
  3. Monitor device and system logs for unusual IOCTL calls or attempts to access session ID information, enabling early detection of exploitation attempts.
  4. Coordinate with device manufacturers and Qualcomm for timely receipt and deployment of security patches once available.
  5. For organizations deploying custom firmware or device management solutions, consider implementing additional cryptographic hardening or validation of session ID generation and transmission.
  6. Educate users and administrators about the risks of installing untrusted applications that could gain local access and exploit this vulnerability.
  7. In high-risk environments, consider network segmentation and endpoint security controls to limit the impact of compromised devices.
  8. Regularly update device firmware and operating systems to incorporate security improvements and reduce attack surface.

Description

Information disclosure when a weak hashed value is returned to userland code in response to a IOCTL call to obtain a session ID.

References

Community reviews

Loading reviews…