Skip to main content
VulnerabilityPublished

CVE-2025-47383: Qualcomm Snapdragon · Missing Cryptographic Step

Affects Qualcomm SnapdragonSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.2 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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
  • APQ8098 – WSA8845
86 affected builds
Fixed in–

AI-suggested

  1. Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-47383 and apply them promptly across all affected devices.
  2. Implement network segmentation and strict access controls to limit exposure of devices using vulnerable Snapdragon platforms, especially restricting access to VoWiFi call initiation services to trusted networks and users.
  3. Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics tuned to detect anomalous VoWiFi call initiation patterns or cryptographic anomalies.
  4. Enforce strong privilege management policies to minimize the risk of privilege escalation that could enable exploitation of this vulnerability.
  5. Use endpoint security solutions capable of monitoring and restricting unauthorized modifications to communication modules or cryptographic configurations.
  6. For organizations deploying Snapdragon-based automotive or IoT devices, ensure secure boot and firmware integrity verification mechanisms are in place to prevent unauthorized firmware tampering.
  7. Educate security teams about the specific risk associated with VoWiFi cryptographic weaknesses and incorporate this vulnerability into incident response plans.
  8. Where feasible, consider alternative communication methods or additional encryption layers at the application level to mitigate risks until patches are available.
  9. Collaborate with vendors to obtain detailed technical guidance and support for remediation efforts.

Description

Weak configuration may lead to cryptographic issue when a VoWiFi call is triggered from UE.

References

Community reviews

Loading reviews…