CVE-2026-106233

chromium-browser: Use after free in Metrics

Published Oct 6, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
Use after free in Metrics in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Analysis

AI-generated

Technical impact

Google Chrome contains a use‑after‑free flaw in the Metrics component. This weakness, identified as CWE-416, permits an attacker who has already compromised a renderer process to run arbitrary code at the level of the Chrome user profile and escape the sandbox. Consequently, an exploited system could be fully compromised, granting the attacker control over data and possibly the host OS.

Affected Systems

It is inferred that the vulnerability affects all desktop installations of Google Chrome prior to 155.0.8059.39, across Windows, macOS, and Linux. Users on stable channel releases before that build are vulnerable; it is inferred that disabling the Metrics feature is a containment measure.

Risk and Exploitability

The CVSS score of 8.3 signals a high severity vulnerability. The EPSS score is not available, and the bug is not listed in the CISA KEV catalog, indicating no public exploitation evidence yet. It is inferred that the flaw requires an attacker to first compromise a renderer process; based on the description, it is inferred that the likely attack vector is compromised renderer processes, which could arise through phishing, drive‑by downloads, or malicious local content—all inferred from typical renderer compromise methods. Once that foothold is achieved, delivering a crafted HTML page can trigger the use‑after‑free, enabling code execution outside the sandbox—an attack that is classically both remote in nature and simple to execute once the initial renderer compromise is achieved. The outlined attack chain suggests several points of failure but also multiple vectors for an adversary, making the risk significant for users who run unpatched Chrome.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Chrome to 155.0.8059.39 or newer to eliminate the vulnerability.
  • Ensure that the renderer sandbox remains active; do not disable or weaken sandboxing policies.
  • If an immediate update is not possible, disable the Metrics feature or block any content that triggers its calls until a patch is applied.

Generated by OpenCVE AI on October 7, 2026 at 04:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4833-1 chromium security update
Debian DSA Debian DSA DSA-6553-1 chromium security update
History
Type Values Removed Values Added
Title Use-After-Free in Chrome Metrics Enables Remote Code Execution via Compromised Renderer chromium-browser: Use after free in Metrics
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Title Use-After-Free in Chrome Metrics Enables Remote Code Execution via Compromised Renderer
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.3, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Use after free in Metrics in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Weaknesses CWE-416
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Oct 7, 2026, 3:55 AM
Reserved
Oct 6, 2026, 4:32 PM
Status
Analyzed
Published
Oct 6, 2026, 7:17 PM
Modified
Oct 7, 2026, 3:25 PM
Severity
Important
Public date
Oct 6, 2026, 6:41 PM