Root code execution via crafted recovery image
Published Mar 6, 2025 · Updated May 8, 2025
Privilege escalation in Google ChromeOS 15786.48.2 allows physically proximate attackers to execute code as root via a recovery image. The Installer and Recovery image path processes a specially crafted image through a root-capable recovery flow; the restricted vendor issue does not disclose the failed validation or affected function. Successful exploitation grants root execution and can remove enterprise enrollment, but requires physical access to a compatible device.
Summary
What happened
Privilege escalation in Google ChromeOS 15786.48.2 allows physically proximate attackers to execute code as root via a recovery image. The Installer and Recovery image path processes a specially crafted image through a root-capable recovery flow; the restricted vendor issue does not disclose the failed validation or affected function. Successful exploitation grants root execution and can remove enterprise enrollment, but requires physical access to a compatible device.
The record
- CVE
- CVE-2025-1121
- Published
- Mar 6, 2025
- Updated
- May 8, 2025
- Vendor
- Product
- ChromeOS
- Classifications
- CWE-269, T1068
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 6, 2025CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record 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=15786.48.2 <15786.48.2
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