dbcve.org
AndroidOperating system · Google

CVE-2026-0063

HIGH · 7.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 setAllowedCarriers of PhoneInterfaceManager.java, there is a possible way to disable carrier restrictions 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 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 logic error in the setAllowedCarriers method of PhoneInterfaceManager.java allows local users to bypass carrier restrictions, enabling unauthorized modification of carrier policies and resulting in local privilege escalation without requiring additional execution privileges or user interaction.

MitigationThis vulnerability requires a code-level fix in PhoneInterfaceManager.java to correct the logic error in setAllowedCarriers that incorrectly allows disabling carrier restrictions; organizations should apply vendor-provided patches for the Android framework once available.

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:= 17.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
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 checks

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

  1. Verify Android version is 17.0
    Run 'getprop ro.build.version.release' via adb shell or check Settings > About Phone > Android version
    Affected if The displayed version equals 17.0 exactly
  2. Check if device has carrier restriction functionality
    Inspect if the device implements carrier restrictions (typically found in Settings > Network & Internet > SIM cards or Settings > Connections > Mobile networks on carrier-locked devices)
    Affected if The device has carrier restriction settings available and the setAllowedCarriers method can be invoked by an application
  3. Verify PhoneInterfaceManager component exposure
    Check if any installed application holds the carrier privilege required to call setAllowedCarriers - review app permissions for 'android.permission.MODIFY_PHONE_STATE' or carrier-specific privileges
    Affected if An application without proper carrier authorization can successfully call setAllowedCarriers and modify carrier restrictions
  4. Test carrier restriction bypass
    Use a test application or adb command to invoke setAllowedCarriers with parameters that disable carrier restrictions and observe if the operation succeeds without proper carrier privilege
    Affected if The setAllowedCarriers method returns success when called without proper carrier authentication, allowing carrier restrictions to be disabled

The environment is affected if running Android 17.0 AND the setAllowedCarriers method in PhoneInterfaceManager can be invoked by an unprivileged local user to bypass carrier restrictions.

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

This vulnerability requires a code-level fix in PhoneInterfaceManager.java to correct the logic error in setAllowedCarriers that incorrectly allows disabling carrier restrictions; organizations should apply vendor-provided patches for the Android framework once available.

Recommended fix Moderate confidence

Android 17.1 or later (patched via Android Security Bulletin)

  1. Check your Android device's current Android version by going to Settings > About Phone > Android version
  2. Verify if your device is running Android 17.0 specifically, as only this version is listed as affected
  3. Check for available system updates: Go to Settings > System > Software Update (or Settings > About Phone > System Update)
  4. If an update is available, download and install it. Android security patches are delivered through monthly updates
  5. For enterprise or managed devices, contact your device administrator or mobile device management (MDM) provider for update availability
  6. If no update is available from your device manufacturer, monitor the Android Security Bulletin for the corresponding patch level fix
Caveat Minimal - monthly security updates typically have no breaking changes; however, some device-specific configurations may need verification after update

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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