How severe is CVE-2025-6177?

CVE-2025-6177 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2025-6177 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-6177?

CVE-2025-6177 affects Google Chrome Os. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-6177?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-6177 have an EU (EUVD) identifier?

Yes. CVE-2025-6177 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18418.

When was CVE-2025-6177 published?

CVE-2025-6177 was published on 2025-06-16 and last updated on 2026-06-17.

CVE-2025-6177

CVE-2025-6177 is a high-severity vulnerability in Google Chrome Os with a CVSS 3.x base score of 7.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-269.

Key facts

Severity: High (CVSS 3.x base score 7.4)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-18418
Weakness: CWE-269
Affected product: Google Chrome Os
Published: 2025-06-16
Last modified: 2026-06-17

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).

Frequently asked questions

What is CVE-2025-6177?: 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).
How severe is CVE-2025-6177?: CVE-2025-6177 has a CVSS 3.x base score of 7.4, rated high severity. It is exploitable over local access with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-6177 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-6177?: CVE-2025-6177 affects Google Chrome Os. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-6177?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-6177 have an EU (EUVD) identifier?: Yes. CVE-2025-6177 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-18418.
When was CVE-2025-6177 published?: CVE-2025-6177 was published on 2025-06-16 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:o:google:chrome_os:16063.45.2:*:*:*:*:*:*:*

More vulnerabilities in Google Chrome Os

CVE-2014-3188 — Critical (CVSS 10.0): Google Chrome before 38.0.2125.101 and Chrome OS before 38.0.2125.101 do not properly handle the interaction of IPC and…
CVE-2014-1708 — Critical (CVSS 10.0): The boot implementation in Google Chrome OS before 33.0.1750.152 does not properly consider file persistence, which…
CVE-2013-2833 — Critical (CVSS 10.0): Use-after-free vulnerability in the O3D plug-in in Google Chrome OS before 26.0.1410.57 allows remote attackers to…
CVE-2013-0915 — Critical (CVSS 10.0): The GPU process in Google Chrome OS before 25.0.1364.173 allows attackers to cause a denial of service or possibly have…
CVE-2012-2864 — Critical (CVSS 10.0): Mesa, as used in Google Chrome before 21.0.1183.0 on the Acer AC700, Cr-48, and Samsung Series 5 and 5 550 Chromebook…
CVE-2012-4050 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Google Chrome OS before 21.0.1180.50 on the Cr-48 and Samsung Series 5 and 5…

All CVEs affecting Google Chrome Os →

Other CWE-269 (Improper Privilege Management) vulnerabilities

CVE-2026-31852 — Critical (CVSS 10.0): Jellyfin is an open-source media system. The code-quality.yml GitHub Actions workflow in jellyfin/jellyfin-ios is…
CVE-2025-20282 — Critical (CVSS 10.0): A vulnerability in an internal API of Cisco ISE and Cisco ISE-PIC could allow an unauthenticated, remote attacker to…
CVE-2025-0505 — Critical (CVSS 10.0): On Arista CloudVision systems (virtual or physical on-premise deployments), Zero Touch Provisioning can be used to gain…
CVE-2023-48418 — Critical (CVSS 10.0): In checkDebuggingDisallowed of DeviceVersionFragment.java, there is a possible way to access adb before SUW…
CVE-2023-48419 — Critical (CVSS 10.0): An attacker in the wifi vicinity of a target Google Home can spy on the victim, resulting in Elevation of Privilege
CVE-2023-31273 — Critical (CVSS 10.0): Protection mechanism failure in some Intel DCM software before version 5.2 may allow an unauthenticated user to…

Browse all CWE-269 (Improper Privilege Management) vulnerabilities →