# CVE-2025-6177: ChromeOS MiniOS Root Code Execution Bypass While Dev Mode Blocked

> Local attackers can gain root code execution on ChromeOS devices via a debug shell bypass, even when developer mode is blocked by policy.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-v9hm-xvm9-qqfr

## What is CVE-2025-6177?

CVE-2025-6177 is a high-severity vulnerability in Google Chrome Os, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Privilege Escalation in MiniOS in Google ChromeOS (16063.45.2 and potentially others) on enrolled devices allows a local attacker to gain root code execution via exploiting a debug shell (VT3 console) accessible through specific key combinations during developer mode entry and MiniOS access, even when developer mode is blocked by device policy or Firmware Write Protect (FWMP).

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-6177?

It affects 1 product.


Products: Google Chrome Os.

## How do I fix CVE-2025-6177?

No fix has been published for CVE-2025-6177 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-6177 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6177 exists.

## Other vulnerabilities in Google Chrome Os

- [CVE-2014-1708](https://insights.sbomify.com/CVE-2014-1708/): Code injection in n/a (critical 10.0)
- [CVE-2013-2833](https://insights.sbomify.com/CVE-2013-2833/): Use after free in n/a (critical 10.0)
- [CVE-2013-0915](https://insights.sbomify.com/CVE-2013-0915/): Integer overflow in n/a (critical 10.0)
- [CVE-2012-2864](https://insights.sbomify.com/CVE-2012-2864/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4050](https://insights.sbomify.com/CVE-2012-4050/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6177 and fix it if it is affected.

What it is: CVE-2025-6177 is a high-severity vulnerability in Google Chrome Os, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6177 exists.

Affected product: Google Chrome Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-6177/ (Markdown: https://insights.sbomify.com/CVE-2025-6177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-6177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-6177
- OSV: https://osv.dev/vulnerability/CVE-2025-6177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-6177/
Summaries are generated and may contain mistakes; the official description above is the record.