Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-106344 Overview
CVE-2026-106344 is a missing authorization vulnerability in the Permissions component of Google Chrome. The flaw affects Chrome versions prior to 155.0.8059.39 and is tracked under CWE-862: Missing Authorization. Google rated the Chromium security severity as Low.
A remote attacker who has already compromised the renderer process can combine the flaw with social engineering to bypass system access restrictions through a crafted HTML page. Exploitation requires both prior renderer compromise and user interaction, which limits practical attack scenarios.
Critical Impact
Attackers chaining a renderer compromise with user-directed social engineering can bypass permission checks and access resources that should require explicit authorization.
Affected Products
- Google Chrome Desktop (Stable channel) prior to 155.0.8059.39
- Chromium-based browsers that incorporate the vulnerable Permissions code
- Downstream distributions pending vendor-specific Chromium rebases
Discovery Timeline
- 2026-10-06 - CVE CVE-2026-106344 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-106344
Vulnerability Analysis
The vulnerability resides in Chrome's Permissions subsystem, which governs access to sensitive browser capabilities such as camera, microphone, geolocation, notifications, and file system APIs. The code path handling certain permission requests fails to enforce the full authorization checks required before granting access.
An attacker who has already compromised the renderer process can issue requests that reach privileged permission flows without passing through the expected validation. The addition of social engineering, such as prompting the user to click a crafted interface element, satisfies any remaining user-gesture requirement. The combined effect is a bypass of system access restrictions that Chrome's permission model is designed to enforce.
See the Chromium Issue Tracker #498375898 for the vendor's technical record.
Root Cause
The root cause is a missing authorization check (CWE-862) in the Permissions component. The code did not verify that the caller held the required authorization before executing a sensitive permission-related action, allowing a compromised renderer to request operations outside its intended privilege boundary.
Attack Vector
Exploitation is a two-stage process. The attacker first compromises the renderer process, typically through a separate memory-corruption or logic bug delivered via a malicious page. The attacker then serves a crafted HTML page that triggers the permission flow and uses social engineering to coax the victim into the interaction needed to bypass system access restrictions.
The vulnerability cannot be exploited by a passive attacker and is not a one-click drive-by. The requirement for a prior renderer compromise plus user interaction is reflected in the low EPSS probability reported for this CVE.
No verified public exploit code is available. Technical details referenced in prose only; see the Google Chrome Stable Update advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-106344
Indicators of Compromise
- Chrome processes running at versions earlier than 155.0.8059.39 across managed endpoints
- Renderer processes spawning unexpected child processes or accessing permission-gated resources such as camera, microphone, geolocation, or local files
- Browser navigation to attacker-controlled HTML pages followed by anomalous permission grants recorded in browser telemetry
Detection Strategies
- Inventory installed Chrome and Chromium-based browser versions and flag any build below 155.0.8059.39
- Correlate browser process telemetry with sudden access to privacy-sensitive device APIs that were not previously used by the site
- Monitor for renderer-process anomalies such as unexpected sandbox escapes, crashes, or IPC patterns indicating a prior compromise stage
Monitoring Recommendations
- Collect Chrome update and version telemetry through EDR and endpoint management tooling
- Forward browser and process events to a central data lake for cross-host correlation and historical hunting
- Alert on social-engineering patterns such as repeated permission prompts originating from newly observed domains
How to Mitigate CVE-2026-106344
Immediate Actions Required
- Update Google Chrome to version 155.0.8059.39 or later on all Windows, macOS, and Linux endpoints
- Restart Chrome after the update so that running renderer processes load the patched Permissions code
- Audit Chromium-based browsers (Edge, Brave, Opera, Vivaldi) and apply vendor updates once rebased on the fixed Chromium release
Patch Information
Google addressed the issue in the Chrome Stable channel at version 155.0.8059.39. Refer to the Google Chrome Stable Update release notes and the Chromium Issue Tracker #498375898 for the fix record. Enterprises managing Chrome via Group Policy or MDM should push the updated channel to all managed devices.
Workarounds
- Enforce automatic Chrome updates through enterprise policy so that patched builds deploy without user action
- Restrict permission prompts for untrusted sites using the DefaultGeolocationSetting, DefaultNotificationsSetting, and related Chrome enterprise policies
- Provide user awareness guidance on declining unexpected permission prompts tied to unfamiliar pages
# Verify installed Chrome version on Linux endpoints
google-chrome --version
# Example Chrome enterprise policy (JSON) to disable risky permission defaults
# Place in /etc/opt/chrome/policies/managed/permissions.json
{
"DefaultGeolocationSetting": 2,
"DefaultNotificationsSetting": 2,
"DefaultSensorsSetting": 2
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

