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

CVE-2026-10940: Race in Codecs in Google Chrome on Windows prior to 149

Race in Codecs in Google Chrome on Windows prior to 149.0.7827.53 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.53
Affected Products
1

Get notified

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

HarborGuard Analysis

Synopsis

A race condition in the Codecs component of Google Chrome on Windows allows a remote attacker who has already compromised the browser's renderer process to escape the sandbox via a crafted HTML page. The attack requires network access and a victim to interact with attacker-controlled content, but no authentication is needed. Successful exploitation gives the attacker full code execution outside the Chrome sandbox, breaking the primary security boundary that contains a compromised renderer. A patched-image rebuild at version 149.0.7827.53 is available on HarborGuard for environments running an affected version.

HarborGuard Coverage

Detection

Detection is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against customer images in registries and CI/CD pipelines, including custom-built images that bundle Chrome or Chromium as a dependency.

Available
Triage

HarborGuard surfaces this CVE with its CVSS v3.1 score of 8.3 (HIGH) and applies per-environment compliance policy weighting to prioritize alert routing to the correct team inbox within each customer organization.

Available
Patch

A patched-image rebuild at Chrome 149.0.7827.53 becomes available on HarborGuard for environments running an affected version the moment the upstream fix is confirmed. For customers who opt into auto-remediation, HarborGuard triggers a 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 must reach the victim over the network, typically by serving a crafted HTML page from a remote host.

  • AuthenticationNot required

    No account or credential is needed; the attack path requires only that the victim loads attacker-controlled content.

  • Victim interactionRequired

    The victim must visit or be redirected to a crafted HTML page, requiring a social-engineering or drive-by delivery step.

  • Attack complexityDetail

    Exploitation is rated AC:H, meaning the attacker must win a race condition in the Codecs component, which depends on precise timing and may require repeated attempts or environmental factors to succeed reliably.

Blast Radius

  • An attacker who wins the race condition escapes the Chrome sandbox on Windows, gaining arbitrary code execution in the context of the browser process outside the sandbox boundary.
  • With sandbox escape achieved, the attacker can read files and credentials accessible to the browser process user account, including stored cookies, saved passwords, and local session tokens.
  • The attacker can write or modify files on the host filesystem within the permissions of the running user, enabling persistence mechanisms such as dropping executables or modifying startup entries.
  • The attacker can crash or disrupt Chrome and any dependent processes, causing denial of service for the affected user session.

How HarborGuard Handles This

Available on HarborGuard: detection for CVE-2026-10940 is active across all connected registries and pipeline stages, with images matched against the affected version range (Chrome below 149.0.7827.53) within minutes of the CVE being published. For environments where the affected Chrome version is present in an image, a rebuild targeting 149.0.7827.53 is queued automatically. For customers who opt into auto-remediation, HarborGuard performs the rebuild, executes a regression run against the patched image, and opens a pull request against affected workloads; median time from CVE publication to merged patch PR for high-severity issues is around 90 minutes in environments with auto-remediation enabled. Where compliance policy requires manual approval, the rebuilt image and regression results are staged and a triage ticket is routed to the designated team inbox for review.

See how HarborGuard automates this

Fix available

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