Local privilege escalation via carrier-restriction bypass
Published Mar 10, 2026 · Updated Mar 10, 2026
Local privilege escalation in Google Android's oobconfig component allows local users to bypass carrier restrictions through a logic error. The public record identifies a logic error in oobconfig but does not disclose the affected function, decision path, or erroneous operation on carrier-controlled input. Exploitation requires local access but no prior execution privileges or user interaction, and the demonstrated consequence is circumvention of carrier restrictions.
Summary
What happened
Local privilege escalation in Google Android's oobconfig component allows local users to bypass carrier restrictions through a logic error. The public record identifies a logic error in oobconfig but does not disclose the affected function, decision path, or erroneous operation on carrier-controlled input. Exploitation requires local access but no prior execution privileges or user interaction, and the demonstrated consequence is circumvention of carrier restrictions.
The record
- CVE
- CVE-2026-0118
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Go standard library
- Product
- Android
- Classifications
- CWE-693, T1404
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 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