CVE-2023-33070: Qualcomm Snapdragon · Improper Authentication
Affects Qualcomm SnapdragonSource CVE Database V5
Not known to be exploited · CVSS 7.1 High.
Data as of 26 Oct 2026, 17:16 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:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Dec 2023
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.
What to do
AI-suggested
- Immediate inventory and identification of all Qualcomm Snapdragon-based devices and platforms within the organization, focusing on automotive OS and embedded systems.
- Engage with Qualcomm and device vendors to obtain and apply security patches or firmware updates as soon as they become available.
- Implement strict access controls and network segmentation to limit local access to vulnerable devices, reducing the risk of exploitation since the attack vector is local.
- Monitor device logs and system behavior for signs of transient DoS or unusual disruptions in secure IO operations.
- For automotive systems, integrate fail-safe mechanisms that maintain critical functions even during transient DoS conditions to mitigate safety risks.
- Collaborate with suppliers to ensure secure update mechanisms are in place for embedded devices to facilitate timely patch deployment.
- Conduct penetration testing and security assessments focusing on local access vectors to identify potential exploitation paths.
- Educate technical teams about the vulnerability specifics to enhance detection and response capabilities.
- Consider deploying runtime protection or anomaly detection tools that can identify and block unauthorized secure IO calls.
- Maintain up-to-date asset management and vulnerability scanning to track affected hardware and firmware versions continuously.
Description
Transient DOS in Automotive OS due to improper authentication to the secure IO calls.