Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessInstall malicious app on device
-
DeliveryInvoke vulnerable SearchRequestDatabaseUtil function
-
ExploitSubmit crafted SQL-injection input
-
ExecutionCrash/corrupt database operation
-
ImpactLocal denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires local access to the device - specifically code already executing on the Android device, such as a malicious or compromised application, since the CVSS vector is AV:L (local). Within that constraint there are no further special conditions: no privileges (PR:N) and no user interaction (UI:N) are required, and no non-default configuration is indicated by the available sources. The scope of impact is limited to local denial of service (A:H only; C:N/I:N) on the affected Android versions (Android 16, Android 17, Android 16-qpr2). The primary limiting factor is the absence of any remote/network path, meaning an attacker must first achieve on-device code execution; the exact triggering code path in SearchRequestDatabaseUtil.java is not described in the available sources beyond 'multiple functions'. |
| Impact | This is a moderate, low-urgency issue (CVSS 6.2) despite the SQL-injection mechanism (CWE-89). The CVSS vector CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H is explicit that the only impact is availability (A:H) via local denial of service - confidentiality and integrity are rated None. This creates a notable tension with the description, which states the flaw allows 'a possible way to access protected data'; the authoritative CVSS scoring (C:N/I:N) does NOT support a confidentiality/data-disclosure outcome, so the practical impact is a local DoS, not data theft - this discrepancy should be verified against the Android bulletin. Exploitation signals all point to low real-world priority: EPSS is 0.12% (2nd percentile), there is no CISA KEV listing, and no public exploit was identified in the provided references. The vuln.today decision label is 'this_month' (routine patch cadence), not act_now or emergency. The limiting factor is the local attack vector (AV:L): exploitation requires code already running on the device (e.g. a malicious or compromised app), not a remote network path, which substantially narrows the realistic threat to scenarios where an attacker already has a foothold. |
| Exploit ScenarioDerived | A malicious or compromised application already installed on an Android device issues crafted input to the vulnerable SearchRequestDatabaseUtil functions, injecting SQL that corrupts or crashes the affected database operation and causes a local denial of service. No user interaction and no additional execution privileges are required (AV:L/PR:N/UI:N). No public proof-of-concept or exploit code was identified in the provided sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Local denial of service in Google Android 16, Android 16-qpr2 and Android 17 is caused by SQL injection (CWE-89) in multiple functions of SearchRequestDatabaseUtil.java, which can be reached by code already running on the device to access protected data and crash or destabilise the affected component. The vector is AV:L/AC:L/PR:N/UI:N with impact limited to availability (A:H), so a malicious or compromised application needs no additional privileges and no user interaction, but there is no remote path. Risk is moderate and low-urgency (CVSS 6.2, EPSS 0.12% / 2nd percentile, no CISA KEV entry), and no public exploit code was identified at time of analysis; the flaw is addressed by the Android Security Bulletin dated 2026-11-01.
RemediationAI
Apply the Android Security Bulletin dated 2026-11-01 (https://source.android.com/docs/security/bulletin/2026/2026-11-01) to bring affected devices running Android 16, Android 16-qpr2 or Android 17 up to a build that contains the SearchRequestDatabaseUtil.java fix - patch available per vendor advisory; the bulletin referenced in the available data does not state a discrete fix version string beyond the bulletin date/patch level, so verify the device's security patch level after updating. The supplied references document no separate workaround, and updating is the complete fix. As a compensating measure only - it does not repair the SQL injection - reduce the local attack surface by restricting app installation to trusted sources and blocking sideloading of untrusted APKs on managed fleets via MDM policy, accepting the trade-off that this limits legitimate developer/sideload workflows while still leaving any already-installed or previously approved malicious app able to reach the vulnerable functions; urgency is this-month rather than emergency, consistent with the low EPSS score and absence of KEV listing.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a classic SQL injection (CWE-89) in Android's search-request database utility layer: several functions in SearchRequestDatabaseUtil.java build database queries without adequate separation of caller-supplied input from SQL syntax, so crafted input can alter the shape of the query and reach data the caller should not be able to read. Because these utility functions sit behind the platform's search/database plumbing on Android, the practical exposure is to code executing locally on the handset - a malicious or trojanised application - rather than to a network peer. The CVSS vector AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H describes only the severity envelope: local attack path, no privileges and no user interaction, unchanged scope, and high availability impact with no confidentiality or integrity impact stated. How the injection is actually triggered, and which of the 'multiple functions' is the entry point, is not described in the available sources; nothing in the supplied data indicates a race condition, timing dependency or non-default configuration requirement. Affected builds are identified by the CPE cpe:2.3:a:google:android and enumerated by the EUVD record as Android 16, Android 16-qpr2 and Android 17.
Know when Android gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Local attacker app with no privileges or interaction triggers a crash, so AV:L/PR:N/UI:N; impact is availability-only DoS (A:H), with C:N/I:N per the stated local DoS outcome.
Primary rating from Vendor (google_android).
CVSS VectorVendor: google_android
Lifecycle Timeline
3DescriptionCVE.org
In multiple functions of SearchRequestDatabaseUtil.java, there is a possible way to access protected data due to SQL injection. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466
Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A
Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp
Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef
Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK
An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows
Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows
luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.
The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01
EUVD-2026-115581
GHSA-mwmj-qf22-73pw
NVD
CVE.org
EPSS
Exploit-DB