HIGH 8.8

CVE-2026-12439: Chrome Use-After-Free in Digital Credentials (Critical) – Patch Guidance

Google Chrome contains a use-after-free vulnerability in its Digital Credentials component that could allow an attacker to corrupt heap memory and potentially execute arbitrary code. The flaw requires user interaction—specifically, visiting a specially crafted webpage—but poses a critical risk because it affects a widely deployed browser across multiple operating systems. Users running Chrome versions prior to 149.0.7827.155 are at risk.

Source data · NVD / CISA · public domain

CVSS
3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-416
Affected products
4 configuration(s)
Published / Modified
2026-06-17 / 2026-06-18

NVD description (verbatim)

Use after free in Digital Credentials in Google Chrome prior to 149.0.7827.155 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-12439 is a use-after-free vulnerability (CWE-416) in the Digital Credentials feature of Chromium/Chrome. Use-after-free flaws occur when freed memory is accessed again, potentially allowing attackers to read sensitive data, write malicious values, or achieve code execution via heap corruption. In this case, a remote attacker can craft a malicious HTML page that triggers the vulnerability when a user visits it. The vulnerability exists in Chrome versions before 149.0.7827.155 and affects the browser engine across Windows, macOS, and Linux platforms. Chromium's security team classified this as Critical severity due to the combination of exploitability and impact.

Business impact

This vulnerability represents a direct threat to organizational endpoints where Chrome is the primary or secondary browser. An attacker could compromise a user's system by hosting malicious content on a website or injecting malicious HTML into a compromised legitimate site. Once executed, the attacker gains the same privileges as the Chrome process, potentially allowing data theft, credential harvesting (particularly sensitive given the Digital Credentials component), malware installation, or lateral movement within a network. Organizations with large Chrome deployments face elevated risk, especially if users frequently visit untrusted websites or if email-based phishing campaigns direct users to malicious content.

Affected systems

Google Chrome prior to version 149.0.7827.155 is directly affected. The vulnerability also affects the underlying platforms: Windows, macOS, and Linux systems running vulnerable Chrome versions. There is no indication this affects Chrome on Android or other Chromium-based browsers at this time, but organizations should verify vendor-specific patch status for Edge, Opera, Brave, and other Chromium derivatives if deployed.

Exploitability

The vulnerability requires user interaction (clicking or navigating to a malicious webpage), which is a moderate barrier but not a high one given common phishing and social engineering tactics. No authentication is required; the attack is triggered purely by visiting a crafted HTML page. The network-based attack vector and low attack complexity make this moderately easy to exploit at scale. The fact that it has not yet been added to the CISA KEV catalog does not diminish its risk—it reflects a recent disclosure rather than current active exploitation, though that status should be monitored closely.

Remediation

Update Google Chrome to version 149.0.7827.155 or later immediately. Organizations should enable automatic Chrome updates where possible and verify deployment across all managed endpoints. For enterprises unable to auto-update, prioritize manual patching within 24–48 hours. Consider supplementary controls: disable or restrict access to Digital Credentials features if organizational policy permits, implement network-level protections (DNS filtering, web content filtering) to reduce exposure to malicious sites, and conduct user awareness training on recognizing phishing and suspicious links.

Patch guidance

Google Chrome version 149.0.7827.155 or later contains the fix. Users can verify their current version by navigating to chrome://settings/help, which will also show update status. Enterprise administrators should deploy this patch through their standard Chrome update mechanisms (Google Admin Console, mobile device management, or group policy) as soon as it is available in the production channel. Verify patch deployment against vendor advisory documentation to ensure all endpoints are running the patched version before considering the vulnerability mitigated.

Detection guidance

Monitor Chrome version compliance across your fleet using endpoint management tools or security information and event management (SIEM) solutions. Correlate browser crash reports or heap corruption signals with visits to suspicious domains; modern browsers log crashes and exceptions that may indicate exploitation attempts. Network detection is challenging without exploit signatures, but web proxies and intrusion detection systems should flag attempts to access known malicious domains hosting CVE-2026-12439 exploits as threat intelligence becomes available. Consider enabling Enhanced Safe Browsing or equivalent features that warn users about malicious content.

Why prioritize this

This vulnerability merits immediate remediation despite its moderate CVSS score of 8.8. The combination of a critical Chromium severity rating, network-based attack vector, low attack complexity, high impact (confidentiality, integrity, and availability all scored as High), and the prevalence of Chrome across enterprise and consumer endpoints elevates actual risk beyond the numerical score. The Digital Credentials feature is increasingly important for secure authentication flows, making compromise of this component particularly damaging. Organizations should treat this as a priority patch target within 48 hours of availability.

Risk score, explained

The CVSS 3.1 score of 8.8 (HIGH severity) reflects a network-accessible vulnerability requiring user interaction, with no privilege escalation required, affecting confidentiality, integrity, and availability. However, the Chromium security team's Critical rating and the use-after-free mechanism's potential for code execution place this at the higher end of the HIGH range. The lack of KEV catalog inclusion does not reduce the intrinsic risk; it indicates the vulnerability is not yet documented as exploited in the wild, a situation that can change rapidly for high-impact browser vulnerabilities.

Frequently asked questions

Do I need to update immediately, or can this wait?

You should prioritize this update within 24–48 hours. While no active widespread exploitation has been publicly reported, use-after-free vulnerabilities in browser memory management are attractive targets for sophisticated attackers. Delaying increases risk, especially for users who visit untrusted or compromised websites.

Does this affect Chrome on my phone or tablet?

The available information specifies Windows, macOS, and Linux platforms. Mobile Chrome versions should be checked separately against vendor release notes; Google typically addresses critical Chromium bugs across platforms, so assume Android and iOS versions may also be affected unless explicitly stated otherwise by Google.

What does 'Digital Credentials' mean, and why does this vulnerability matter there?

Digital Credentials is Chrome's feature for managing and using authentication credentials (like passkeys and FIDO2 credentials). A compromise here could allow attackers to steal or misuse credentials, potentially bypassing strong authentication defenses that organizations rely on.

If I don't use Digital Credentials, am I still at risk?

Yes. The vulnerability exists in the Digital Credentials component, but exploitation could still lead to heap corruption and broader code execution, regardless of whether you actively use credential features. You are still vulnerable and should patch.

This analysis is based on official CVE data and vendor disclosures as of the publication date. Patch versions, vendor advisories, and KEV catalog status are subject to change; verify all patch versions and deployment guidance against the latest official sources from Google and your organization's patch management system before proceeding. SEC.co does not provide guarantee of exploit availability, active exploitation status, or real-world attack data. Organizations are responsible for assessing applicability within their environment and determining remediation timelines based on risk tolerance, network exposure, and business criticality. Source: NVD (public-domain), retrieved 2026-07-26. Analysis generated by SEC.co (claude-haiku-4-5).