Skip to main content
VulnerabilityPublished

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

Affects Qualcomm SnapdragonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
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:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Qualcomm, Inc.SnapdragonAffected
  • QCA6391 – WSA8845
22 affected builds
Fixed in–

AI-suggested

  1. Monitor Qualcomm advisories closely for official patches or firmware updates addressing CVE-2025-47378 and apply them promptly across all affected devices.
  2. Implement strict access controls and privilege separation on devices using affected Snapdragon platforms to limit the ability of low-privileged processes to access sensitive system components.
  3. Employ runtime integrity monitoring and anomaly detection to identify unauthorized access attempts to boot loader or cryptographic material.
  4. Use hardware-backed security features such as Trusted Execution Environments (TEE) and secure boot to reinforce isolation between HLOS and boot loader components.
  5. For enterprise deployments, enforce device management policies that restrict installation of untrusted software and monitor device firmware integrity.
  6. Coordinate with device manufacturers and vendors to ensure timely updates and security patches are integrated into device firmware.
  7. Consider network segmentation and endpoint detection to reduce the attack surface and detect lateral movement if exploitation occurs.
  8. Educate security teams about the specific nature of this vulnerability to enhance incident response readiness.

Description

Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain.

References

Community reviews

Loading reviews…