CVE-2025-47383: Qualcomm Snapdragon · Missing Cryptographic Step
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 30 Oct 2026, 11:52 UTC
- 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:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Qualcomm, Inc.Snapdragon | Affected
| Fixed in– |
AI-suggested
- Monitor Qualcomm and device manufacturers for official patches or firmware updates addressing CVE-2025-47383 and apply them promptly across all affected devices.
- 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.
- Employ intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics tuned to detect anomalous VoWiFi call initiation patterns or cryptographic anomalies.
- Enforce strong privilege management policies to minimize the risk of privilege escalation that could enable exploitation of this vulnerability.
- Use endpoint security solutions capable of monitoring and restricting unauthorized modifications to communication modules or cryptographic configurations.
- 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.
- Educate security teams about the specific risk associated with VoWiFi cryptographic weaknesses and incorporate this vulnerability into incident response plans.
- Where feasible, consider alternative communication methods or additional encryption layers at the application level to mitigate risks until patches are available.
- 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.