AndroidOperating system · Google

CVE-2026-0026

HIGH · 7.8 CVSS v3.1 Published 2026-03-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
In removePermission of PermissionManagerServiceImpl.java, there is a possible way to override any system permission due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is 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 confidence

In the PermissionManagerServiceImpl.java's removePermission function, a logic error allows a local attacker to override system permissions, potentially enabling privilege escalation without requiring additional execution privileges.

MitigationApply vendor-supplied security patch for the PermissionManagerService; verify permission integrity after patch deployment.

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
AndroidOperating system
Affected:= 14.0

CVSS 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version is 14.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The device is running Android version 14.0 exactly (not 14.0.1, 14.0.2, or other point releases)
  2. Confirm the vulnerability is in PermissionManagerService
    This check requires source code review or checking vendor security bulletin for CVE-2026-0026 details. The flaw exists in PermissionManagerServiceImpl.java's removePermission function.
    Affected if The installed Android 14.0 build does not have the vendor security patch for this specific vulnerability in PermissionManagerService.
  3. Audit recent permission changes
    Check system logs (logcat) for unusual permission modifications via PermissionManagerService, or review /data/system/users/*/runtime-permissions.xml for unexpected system permission grants
    Affected if Unexpected modifications to system permissions are present that were not initiated by legitimate system updates or user actions.
  4. Check for signs of local privilege escalation
    Review installed apps for those with unexpectedly elevated privileges, and check /data/app/*/lib directory for any suspicious native libraries that may have been injected
    Affected if Apps exist with system-level permissions they should not have, or unknown native libraries are present that could indicate exploitation.

A device is affected if it runs Android version 14.0 and lacks the vendor security patch for CVE-2026-0026 in PermissionManagerService.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied security patch for the PermissionManagerService; verify permission integrity after patch deployment.

Recommended fix Moderate confidence

Android 15 or later security patch level for Android 14

  1. 1. Navigate to Settings on the Android device
  2. 2. Go to System > Software Update (or Settings > About Phone > System Update)
  3. 3. Check for available updates and download the latest Android security patch or OS update
  4. 4. Install the update and restart the device
Caveat May include new UI changes, feature modifications, or deprecated APIs from Android 15

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0026 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0026 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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