CVE-2026-0091
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn multiple locations, there is a possible way to execute code in the launcher process due to an over-privileged shell user. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA local privilege escalation vulnerability exists where an over-privileged shell user can execute arbitrary code within a launcher process across multiple code locations. This allows a local attacker to elevate their privileges without requiring any user interaction or additional execution privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 14.0= 15.0= 16.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The version listed is 14.0, 15.0, or 16.0 exactly (not a later security patch level)
-
Identify if shell-level access exists on the deviceRun 'whoami' or 'id' via ADB shell to determine the current user contextAffected if The current user context is 'shell' or a similarly unprivileged user without root access
-
Examine launcher process privilegesRun 'ps -A | grep launcher' to find the launcher process, then check its SELinux context with 'ls -laZ /data/data/*launcher*' or similarAffected if The launcher process runs with elevated SELinux domains or permission contexts that exceed standard app permissions
-
Verify shell user can execute code in launcher contextAttempt to identify if the shell user can interact with launcher components via 'dumpsys package' for launcher permissionsAffected if Shell user has access to launcher components or services that should require elevated privileges
A device is affected if it runs Android 14.0, 15.0, or 16.0 AND has a shell user that can interact with the launcher process without proper permission controls in place.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict shell user privileges and implement proper privilege separation in the launcher process; audit and harden permissions across all affected code paths to prevent unauthorized code execution.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0091 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data