HarborGuardharborguardDatabase
Back to search
CRITICALCVE-2026-11250Published Modified CNA Chrome

CVE-2026-11250: Inappropriate implementation in DevTools in Google Chrome prior to 149

Inappropriate implementation in DevTools in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)

Metrics

CVSS v3.1
9.6
Severity
CRITICAL
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

An inappropriate implementation flaw in the DevTools component of Google Chrome (versions prior to 149.0.7827.53) allows a remote attacker who has already compromised the renderer process to extract sensitive data from process memory by loading a crafted HTML page. The attack is reachable over the network, requires no authentication, but does require the victim to interact with a malicious page. Successful exploitation gives the attacker high-confidence access to confidential data, the ability to tamper with content, and the ability to disrupt the affected service. A patched-image rebuild at version 149.0.7827.53 is available on HarborGuard for affected environments.

HarborGuard Coverage

Detection

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

Available
Triage

HarborGuard scores this CVE at CVSS 9.6 (Critical) and applies per-environment compliance policy weighting to surface it at the correct priority level, routing findings to the appropriate team inbox within each customer organization.

Available
Patch

A patched-image rebuild pinned to Chrome 149.0.7827.53 becomes available through HarborGuard once the fix version is confirmed. For customers who opt into auto-remediation, HarborGuard performs the rebuild, runs a regression test suite, and opens a PR against affected workloads automatically.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker delivers the exploit over the network by directing the victim to a crafted HTML page; the Chrome instance must be reachable through normal browser activity.

  • AuthenticationNot required

    No account credentials or prior authentication are needed to initiate the attack against the target.

  • Victim interactionRequired

    The victim must visit or be redirected to the attacker-controlled HTML page, making this a social-engineering or drive-by scenario.

  • Attack complexityDetail

    Attack complexity is low, meaning the exploit is reliable and does not depend on race conditions, specific memory layouts, or other hard-to-control environmental factors; however, a pre-compromised renderer process is a prerequisite.

Blast Radius

  • The attacker reads sensitive data directly from Chrome process memory, including session tokens, credentials, or other in-memory content.
  • The attacker achieves high-integrity impact, meaning in-memory or rendered content can be modified or injected after the renderer compromise is leveraged.
  • The affected Chrome process can be crashed or rendered unavailable, disrupting the user session entirely.
  • Because the CVSS scope is Changed, impact can extend beyond the compromised renderer to other browser components or co-located processes.

How HarborGuard Handles This

Available on HarborGuard: any container image found to include a Chrome binary older than 149.0.7827.53 is flagged immediately upon CVE ingestion. Where compliance policy permits, HarborGuard can trigger an automated rebuild at the patched version, execute a regression run against the rebuilt image, and open a pull request against the affected workload repository. For environments with auto-remediation enabled, the median time from CVE publication to a merged patch PR for critical-severity issues is around 90 minutes. For environments where auto-remediation is not enabled, the finding is queued in the HarborGuard dashboard with full CVSS context, affected layer details, and a direct link to the Chrome 149.0.7827.53 release notes so the responsible team can act manually. Given the Changed scope and the Critical CVSS score, prioritizing this fix ahead of lower-severity queue items is warranted.

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:L/PR:N/UI:R/S:C/C:H/I:H/A:H