dbcve.org
AndroidOperating system · Google

CVE-2026-0034

HIGH · 8.4 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 →
89/100
Remediation priority · High
No privileges Zero-click

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 setPackageOrComponentEnabled of ManagedServices.java, there is a possible notification policy desync due to improper input validation. 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 confidence

A vulnerability in the setPackageOrComponentEnabled method of ManagedServices.java allows improper input validation that can cause notification policy desync, enabling local privilege escalation without requiring additional execution privileges or user interaction.

MitigationApply the latest Android security patch from the device manufacturer; this is a system-level vulnerability requiring a platform-level fix rather than application-level changes.

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= 15.0= 16.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'adb shell getprop ro.build.version.release'
    Affected if Version displayed is exactly 14.0, 15.0, or 16.0 (note: this CVE specifies exact version matches, not version ranges)
  2. Confirm ManagedServices component accessibility
    The vulnerable setPackageOrComponentEnabled method in ManagedServices.java is part of the Android system framework (PackageManagerService). This is a system-level service, not an optional module.
    Affected if The Android framework is running and the PackageManagerService is active (default state on affected versions)
  3. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'adb shell getprop ro.build.version.security_patch'
    Affected if The security patch level is earlier than the published fix date for this CVE (exact date varies by device manufacturer and carrier release)
  4. Verify notification policy status
    Run 'adb shell dumpsys notification' and look for PackageManager policy entries related to ManagedServices
    Affected if The device is running an affected Android version and the notification policy can be manipulated through the vulnerable method

Device is affected if running Android 14.0, 15.0, or 16.0 AND the security patch level predates the CVE-2026-0034 fix release for your specific device model

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 the latest Android security patch from the device manufacturer; this is a system-level vulnerability requiring a platform-level fix rather than application-level changes.

Recommended fix Moderate confidence

Android 17 (latest stable release) or the latest available Android security update for your device model

  1. 1. Check the latest Android Security Bulletin for CVE-2026-0034 for specific patch details
  2. 2. Apply the monthly Android security patch level that addresses this vulnerability
  3. 3. For affected devices, verify the patch has been applied by checking Settings > About Phone > Android version or Security patch level
  4. 4. If the device is no longer receiving security updates, consider upgrading to a device that receives regular monthly security updates
Caveat Major Android version upgrades may introduce UI changes or remove compatibility with older apps

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-0034 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