CVE-2026-10906: Use after free in WebAuthentication in Google Chrome prior to 149
Use after free in WebAuthentication in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Metrics
- CVSS v3.1
- 7.5
- Severity
- HIGH
- Fixed in
- 149.0.7827.53
- Affected Products
- 1
HarborGuard Analysis
Synopsis
A use-after-free vulnerability in the WebAuthentication component of Google Chrome (versions before 149.0.7827.53) allows a remote attacker to corrupt heap memory. Exploitation requires no authentication but depends on the victim performing specific UI gestures after visiting a crafted HTML page; the CVSS vector (AV:N/AC:H/PR:N/UI:R) reflects that the attacker must reach the user's browser over the network and engineer that interaction under high-complexity conditions. Successful exploitation gives the attacker full read, write, and denial-of-service capability over the affected browser process. A patched-image rebuild at version 149.0.7827.53 is available on HarborGuard for environments running an affected version of Chrome.
HarborGuard Coverage
Detection of CVE-2026-10906 is available across every HarborGuard environment; the CVE is ingested from upstream feeds within minutes of publication and matched against customer images in both registries and CI/CD pipelines, including custom-built images that bundle a Chrome or Chromium binary.
AvailableHarborGuard scores this CVE at 7.5 HIGH (CVSS v3.1) and is capable of weighting that score against each customer environment's compliance policy to surface it to the appropriate team inbox without manual routing.
AvailableA patched-image rebuild pinned to Chrome 149.0.7827.53 becomes available on HarborGuard once an affected image is identified. For customers with auto-remediation enabled, HarborGuard can trigger a rebuild, run regression tests, and open a PR against affected workloads automatically.
AvailableExploit Conditions
- Network reachabilityRequired
The attacker must reach the victim's browser over the network by serving a crafted HTML page from a remote origin.
- AuthenticationNot required
No account or credential is needed; the attack is launched from an unauthenticated remote position.
- Victim interactionRequired
The victim must visit the attacker-controlled page and perform specific UI gestures as directed, making social engineering a prerequisite.
- Attack complexityDetail
Complexity is rated High, meaning the attacker must time or arrange the exploit around conditions such as precise heap layout or race conditions that are not entirely under their control.
Blast Radius
- A successful attacker reads sensitive data from the browser process, including stored credentials, session tokens, and page content from any open origin.
- A successful attacker writes to heap memory in the Chrome process, allowing arbitrary code injection or modification of authentication state.
- The attacker can crash the browser process entirely, denying the user access to all open tabs and web-based applications.
- Because the vulnerability sits in the WebAuthentication component, attacker-controlled code runs in a context with access to in-flight FIDO/passkey operations.
How HarborGuard Handles This
Available on HarborGuard: detection runs automatically against any customer image containing a Chrome or Chromium binary, including internally built images, within minutes of CVE publication. For environments where an affected version (below 149.0.7827.53) is found, a rebuilt image at the fixed version is available. Where compliance policy permits auto-remediation, HarborGuard can execute the full flow: rebuild the image, run a regression-test suite, and open a PR against the affected workload. For high-severity CVEs, the median time from publication to a merged patch PR in environments with auto-remediation enabled is around 90 minutes. Customers who have not enabled auto-remediation will see the finding in their HarborGuard dashboard scored at 7.5 HIGH, routed according to their configured policy, with a direct link to the fix version.
Fix available
- Google / Chrome< 149.0.7827.53 (from 149.0.7827.53)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H