What is the CVSS score of CVE-2025-6179?

CVE-2025-6179 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Chrome are affected by CVE-2025-6179?

A critical vulnerability in Google ChromeOS (CVE-2025-6179) allows local attackers to bypass security controls, disable extensions, and gain unauthorized Developer Mode access on managed devices.

Is there a public PoC exploit available for CVE-2025-6179?

Yes, a public proof-of-concept exploit is available for CVE-2025-6179. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-6179?

Within 24 hours: Inventory all ChromeOS devices running version 16181.27.0 and restrict physical access to managed devices; disable local login where possible and enforce screen lock policies. Within 7 days: Implement network segmentation to limit lateral movement from compromised ChromeOS devices; audit extension policies and enforce mandatory extension allowlists via admin console. Within 30 days: Monitor Google for patch availability and establish an expedited deployment process; conduct forensic review of devices for unauthorized extension installations or Developer Mode activation.

Chrome CVE-2025-6179

EUVD-2025-18417 CRITICAL

Incorrect Default Permissions (CWE-276)

2025-06-16 7f6e188d-c52a-4a19-8674-3c3fa7d1fc7f

Privilege Escalation Denial Of Service Chrome Google Chrome Os

9.8

CVSS 3.1

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 21:59 euvd

EUVD-2025-18417

Analysis Generated

Mar 14, 2026 - 21:59 vuln.today

PoC Detected

Jul 02, 2025 - 18:23 vuln.today

Public exploit code

CVE Published

Jun 16, 2025 - 17:15 nvd

CRITICAL 9.8

DescriptionNVD

Permissions Bypass in Extension Management in Google ChromeOS 16181.27.0 on managed Chrome devices allows a local attacker to disable extensions and access Developer Mode, including loading additional extensions via exploiting vulnerabilities using the ExtHang3r and ExtPrint3r tools.

AnalysisAI

Critical permissions bypass vulnerability in Google Chrome OS 16181.27.0 that allows local attackers to disable extensions and gain unauthorized access to Developer Mode on managed Chrome devices. The vulnerability is exploited using the ExtHang3r and ExtPrint3r tools to load arbitrary extensions, affecting enterprise-managed deployments with a CVSS score of 9.8 (critical severity). Active exploitation status and proof-of-concept availability should be verified through CISA KEV and security advisories.

Technical ContextAI

This vulnerability exploits improper access control in Chrome OS's extension management subsystem (CWE-276: Incorrect Default Permissions). The ExtHang3r and ExtPrint3r tools leverage weaknesses in the extension permission validation framework, specifically in how Chrome OS enforces extension policies on managed devices. The affected component is Chrome OS version 16181.27.0, which fails to properly validate user privileges before allowing extension disablement and Developer Mode access. The root cause is insufficient authorization checks in the extension management API, allowing local processes to bypass policy enforcement mechanisms that should restrict these operations to administrators or verified system processes. This is particularly severe on managed Chrome devices where extension policies are centrally enforced through enterprise policies.

RemediationAI

Immediate actions: (1) Apply Chrome OS security updates beyond version 16181.27.0 - verify patch version from Google Chrome OS releases and LTSB branches. (2) For managed devices, enforce extension policies via admin console: disable extension installation, block Developer Mode access, and enforce policy enforcement. (3) Implement network segmentation to restrict local attack vectors and reduce lateral movement potential. (4) Monitor for suspicious extension installation attempts and Developer Mode activations using Chrome Device Management logs. (5) Temporarily disable or restrict user access to affected Chrome OS 16181.27.0 devices until patches are applied. Patch availability should be confirmed at https://chromereleases.googleblog.com/ and applied to all managed Chrome device fleet. Consider mandatory enrollment in Chrome OS auto-update to prevent version stalling.

More from same product – last 7 days

CVE-2026-44739 HIGH This Week

8.7 May 27

SQL injection in Pimcore's CustomReportsBundle (versions ≤ 12.3.5) lets an authenticated user holding the reports_config

CVE-2026-8842 MEDIUM This Month

6.4 May 27

Stored Cross-Site Scripting in the Google+ Link Name WordPress plugin (versions up to and including 1.0) allows authenti

CVE-2025-68712 MEDIUM This Month

5.5 May 27

Authentication bypass in SpSoft AppLock 7.9.40 for Android allows a local attacker with physical device access to circum

CVE-2026-7552 MEDIUM This Month

5.3 May 28

Authorization bypass in the Geo Mashup WordPress plugin (all versions ≤ 1.13.19) exposes sensitive plugin configuration

CVE-2025-68709 MEDIUM This Month

5.2 May 26

Arbitrary JavaScript execution in SailingLab AppLock 4.3.8 for Android is triggered by a malicious co-installed app send

CVE-2025-6179 vulnerability details – vuln.today

Back

Chrome CVE-2025-6179

CVSS VectorNVD

Lifecycle Timeline

DescriptionNVD

AnalysisAI

Technical ContextAI

RemediationAI

More from same product – last 7 days

Share

External POC / Exploit Code