Qualcomm Snapdragon improper validation of syntactic correctness of input

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Qualcomm Snapdragon. It has been classified as critical. This vulnerability affects unknown code. The manipulation leads to improper validation of syntactic correctness of input. This vulnerability is traded as CVE-2026-24087. It is possible to launch the attack on the physical device. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Qualcomm Snapdragon (unknown version) and classified as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a improper validation of syntactic correctness of input vulnerability. Using CWE to declare the problem leads to CWE-1286. The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax. Impacted is confidentiality, integrity, and availability.

It is possible to read the advisory at docs.qualcomm.com. The identification of this vulnerability is CVE-2026-24087 since 01/21/2026. The exploitation is known to be easy. Attacking locally is a requirement. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available.

Upgrading eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.7
VulDB Meta Temp Score: 6.6

VulDB Base Score: 6.2
VulDB Temp Score: 5.9
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.2
CNA Vector (qualcomm): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Improper validation of syntactic correctness of input
CWE: CWE-1286 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒

Physical: Yes
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Timelineinfo

01/21/2026 CVE reserved
06/02/2026 +131 days Advisory disclosed
06/02/2026 +0 days VulDB entry created
06/02/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: qualcomm.com

Advisory: docs.qualcomm.com
Status: Confirmed

CVE: CVE-2026-24087 (🔒)
GCVE (CVE): GCVE-0-2026-24087
GCVE (VulDB): GCVE-100-367799

Entryinfo

Created: 06/02/2026 08:10
Changes: 06/02/2026 08:10 (61)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!