The `ClusterRenderingService.dump()` method, accessible to processes holding `android.permission.DUMP` and…
An Android elevation-of-privilege flaw in ClusterRenderingService.dump(), reachable by processes holding android.permission.DUMP. Fixed in Android 14, 15, 16, 16-qpr2 and 17.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 14, 15, 16, 16-qpr2, 17
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 0/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 14, 15, 16, 16-qpr2, 17
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
This vulnerability affects the Android operating system's ClusterRenderingService component, which handles instrument cluster display rendering. An app that holds certain diagnostic and usage-statistics permissions could use it to change a protected system display setting, allowing it to create persistent overlay displays and inject input events into the cluster screen.
Read the original description
The `ClusterRenderingService.dump()` method, accessible to processes holding `android.permission.DUMP` and `android.permission.PACKAGE_USAGE_STATS`, acts as a confused deputy. It allows attackers to write arbitrary values to `Settings.Global.OVERLAY_DISPLAY_DEVICES`, an operation normally requiring `android.permission.WRITE_SECURE_SETTINGS`, enabling persistent creation of system overlay displays and injection of key events into the cluster UI.
What to do
Upgrade to a fixed version: 14, 15, 16, 16-qpr2, 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15, 14
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-49903
What does this mean?
The ClusterRenderingService.dump() method can be reached by processes that hold the android.permission.DUMP permission. The flaw lets such a process gain privileges beyond what it should have.Source: source.android.com
Am I affected, and how do I check?
The checked facts list Android as the product but give no version ranges or setup conditions, so the exact affected builds are not stated here. To check a device, open Settings > About phone and note the Android version and security patch level, then compare them with the advisory's fixed releases.Source: source.android.com
What should I do about it?
Update to a fixed Android release for your branch: 14, 15, 16, 16-qpr2 or 17. No workaround is recorded in the checked facts.Source: source.android.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data