Description
Use after free in DigitalCredentials in Google Chrome prior to 149.0.7827.155 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)
Published: 2026-06-17
Score: 8.3 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A use‑after‑free flaw in the DigitalCredentials component of Google Chrome allows a remote attacker who has already compromised the renderer process to construct a specially crafted HTML page that may trigger a sandbox escape. This vulnerability is a classic example of CWE‑416, with the potential to break out of the restrictive renderer sandbox, thereby risking arbitrary code execution and full system compromise. The flaw grants the attacker elevated privileges beyond the confined browser context, leading to privilege escalation and data exfiltration.

Affected Systems

Google Chrome browsers prior to version 149.0.7827.155 are vulnerable. The issue is confined to the renderer process in Chrome on desktop platforms. No other vendors or product lines were reported to be affected.

Risk and Exploitability

The CVSS score of 8.3 indicates high severity. The EPSS score of <1% suggests that active exploitation of this flaw is currently unlikely, though the possibility remains. This vulnerability is not listed in CISA's KEV catalog. Based on the description, the attack vector is inferred to be a crafted HTML page accessed by an attacker who first breaches the renderer process. Without the renderer compromise, the flaw is not exploitable. The combination of remote code execution potential and a low exploitation probability results in a moderate overall risk to affected users.

Generated by OpenCVE AI on June 17, 2026 at 18:15 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Google Chrome to the latest stable release, at least 149.0.7827.155 or newer, which contains the remediation for the use‑after‑free bug.
  • Verify that the browser’s sandboxing feature for renderer processes is enabled, ensuring that any breach does not compromise the host operating system.
  • If an immediate update is not possible, consider configuring Chrome policies to restrict the renderer process or isolate it further through additional runtime restrictions such as enhanced content security policies.

Generated by OpenCVE AI on June 17, 2026 at 18:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 17 Jun 2026 13:30:00 +0000

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'}


Wed, 17 Jun 2026 07:00:00 +0000

Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome

Wed, 17 Jun 2026 05:15:00 +0000

Type Values Removed Values Added
Description Use after free in DigitalCredentials in Google Chrome prior to 149.0.7827.155 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)
Weaknesses CWE-416
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Chrome

Published:

Updated: 2026-06-17T13:03:02.746Z

Reserved: 2026-06-16T19:38:28.227Z

Link: CVE-2026-12451

cve-icon Vulnrichment

Updated: 2026-06-17T13:03:00.274Z

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-17T06:45:03Z

Weaknesses