Local privilege escalation via carrier-restriction bypass
Published May 27, 2025 · Updated Feb 26, 2026
Protection mechanism failure in Google Android oobconfig allows local users to gain elevated privileges by bypassing carrier restrictions. The Pixel oobconfig component enforces carrier restrictions incorrectly, but Google has not disclosed the unusual root cause or the specific check that fails. The attack is local to an affected Pixel-family device and requires neither additional execution privileges nor user interaction; elevated access can fully compromise the device.
Summary
What happened
Protection mechanism failure in Google Android oobconfig allows local users to gain elevated privileges by bypassing carrier restrictions. The Pixel oobconfig component enforces carrier restrictions incorrectly, but Google has not disclosed the unusual root cause or the specific check that fails. The attack is local to an affected Pixel-family device and requires neither additional execution privileges nor user interaction; elevated access can fully compromise the device.
The record
- CVE
- CVE-2025-27700
- Published
- May 27, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Android
- Classifications
- CWE-693, T1626
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Android kernel
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo