HarborGuardharborguardDatabase
Back to search
HIGHCVE-2026-12031Published Modified CNA Chrome

CVE-2026-12031: Inappropriate implementation in Views in Google Chrome on Windows prior to 149

Inappropriate implementation in Views in Google Chrome on Windows prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Metrics

CVSS v3.1
8.3
Severity
HIGH
Fixed in
149.0.7827.115
Affected Products
1

Get notified

Email me when this CVE is updated: new fix versions, severity changes, or any record change.

HarborGuard Analysis

Synopsis

This is a sandbox escape vulnerability in the Views component of Google Chrome on Windows, affecting versions prior to 149.0.7827.115. An attacker who has already compromised the Chrome renderer process can reach this flaw remotely, without any credentials, by convincing a user to visit a crafted HTML page. Successful exploitation breaks out of the browser sandbox, giving the attacker code execution capabilities on the underlying host beyond what the renderer normally permits. A patched-image rebuild at version 149.0.7827.115 is available on HarborGuard for affected environments.

HarborGuard Coverage

Detection

Detection of CVE-2026-12031 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of publication from upstream feeds, including custom-built images that bundle Chrome on Windows base layers. Any image carrying a Chrome version below 149.0.7827.115 is flagged automatically during both registry scans and CI pipeline checks.

Available
Triage

HarborGuard scores this CVE at 8.3 HIGH using the CVSS v3.1 vector and weights it against each customer environment's compliance policy to determine urgency and routing. Findings are surfaced to the appropriate team inbox within each customer organization based on image ownership and policy thresholds configured by that organization.

Available
Patch

A patched-image rebuild at Chrome 149.0.7827.115 becomes available on HarborGuard for any environment running an affected version once the upstream fix is confirmed. For customers who opt into auto-remediation, HarborGuard performs the rebuild, runs a regression test suite against the updated image, and opens a pull request against affected workloads automatically.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker delivers the crafted HTML page over the network, requiring the victim's browser to reach attacker-controlled content.

  • AuthenticationNot required

    No credentials or account access are needed; the attack is reachable by any unauthenticated remote party.

  • Victim interactionRequired

    The victim must navigate to or open a crafted HTML page, requiring social engineering or a malicious link to trigger the exploit.

  • Attack complexityDetail

    Attack complexity is high, meaning the attacker must have already compromised the renderer process before this sandbox escape becomes reachable, introducing a significant prerequisite.

Blast Radius

  • Attacker breaks out of the Chrome renderer sandbox and gains code execution on the underlying Windows host.
  • Confidential data accessible to the host process, including stored credentials, files, and session material, becomes readable.
  • The attacker can write or modify files and system state on the host, including persisted application data.
  • The host process and dependent services can be crashed or disrupted, causing denial of service beyond the browser tab.

How HarborGuard Handles This

Available on HarborGuard: detection for CVE-2026-12031 runs against all customer images as soon as the CVE is ingested from upstream feeds, covering any image that bundles Chrome on a Windows base layer. Where compliance policy permits, customers with auto-remediation enabled receive a rebuilt image at Chrome 149.0.7827.115, a regression test run against that image, and a pull request opened against affected workloads; median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes for environments with auto-remediation enabled. For customers who manage patching manually, HarborGuard surfaces the finding with full CVSS context and links to the upstream Chromium advisory so that prioritization and scheduling can proceed without delay. Given that exploitation requires a prior renderer compromise, organizations may also consider network-policy controls that restrict outbound connections from browser workloads as a compensating measure while patch deployment is in progress.

See how HarborGuard automates this

Fix available

149.0.7827.115
Affected packages
  • Google / Chrome
    < 149.0.7827.115 (from 149.0.7827.115)
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H