CVE-2026-9947: Chrome XML Use-After-Free Remote Code Execution

Technical summary

CVE-2026-9947 is a use-after-free vulnerability (CWE-416) in Chrome's XML parsing subsystem. The flaw occurs when the XML processor references memory that has already been freed, allowing an attacker to control the contents of that freed memory and execute arbitrary code. The vulnerability is reachable via a remote vector with no authentication required and only user interaction (clicking a link) needed to trigger it. Although execution occurs within Chrome's sandboxed renderer process, this confinement can potentially be bypassed through additional vulnerabilities or misconfigurations. The Chromium security team rated this as High severity.

Business impact

Organizations must prioritize patching because this vulnerability can lead to data exfiltration from compromised user sessions, credential theft, and potential lateral movement if combined with sandbox escape techniques. For enterprises relying on Chrome for accessing sensitive systems or cloud applications, each unpatched user represents a direct attack surface. Incident response teams should assume that successful exploitation could result in compromise of session cookies, cached credentials, and locally stored authentication tokens. The social engineering ease—convincing users to click a link—makes this a practical threat in targeted campaigns.

Affected systems

The vulnerability affects Google Chrome versions earlier than 148.0.7778.216. It is present on systems running Windows, macOS, and Linux operating systems. Any organization or individual using Chrome on these platforms is at risk until the patch is applied. Users of Chromium-based browsers (Edge, Brave, Opera, etc.) should verify whether their vendor has back-ported the security fix from upstream Chromium.

Exploitability

The vulnerability requires user interaction (clicking a malicious link or visiting a compromised website), making it unsuitable for wormlike propagation but well-suited to targeted phishing campaigns. No patch bypass or special configuration is required—default Chrome installations are vulnerable. The attack surface is broad because any website the user visits could serve the exploit payload. The vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog, but the high CVSS score and straightforward exploitation path suggest that working exploits may be developed or already exist in closed attack communities.

Remediation

Update Google Chrome to version 148.0.7778.216 or later. Chrome will auto-update if automatic updates are enabled; administrators should verify completion on all endpoints. For enterprises with managed deployments, push the update through endpoint management tools and verify rollout before considering the issue resolved. Users on macOS and Linux should similarly verify their Chrome version through Settings > About Google Chrome, which will show the current version and any available updates.

Patch guidance

Apply Chrome version 148.0.7778.216 or any subsequent release. Verify the patch by navigating to Chrome Settings > About Google Chrome; the browser will automatically check for updates and display the installed version. For Windows domain-joined environments, use group policy to manage Chrome updates centrally. macOS administrators can use configuration profiles or third-party management tools. Linux administrators should ensure the system package manager or official Google Chrome repository is configured to deliver the patched version. Test patch deployment in a small cohort before full rollout to catch any compatibility issues with internal web applications.

Detection guidance

Monitor for visits to known malicious sites hosting this exploit, though the initial payload delivery may be obfuscated. Watch for unusual Chrome process behavior such as unexpected child process creation or attempts to access sensitive files. Endpoint detection and response (EDR) solutions should flag Chrome renderer process crashes followed by rapid restarts, which can indicate exploitation attempts. Network-level detection is limited because the malicious HTML is delivered over standard HTTPS. Prioritize endpoint telemetry and user education; alert users to report suspicious web pages or unexpected browser hangs before exploitation completes.

Why prioritize this

This vulnerability merits immediate patching because it combines network reachability, low interaction requirements, and high impact. The CVSS 8.8 score reflects the confluence of network attack vector, no privilege requirement, and high confidentiality/integrity/availability impact. Although the sandbox provides some containment, the practical risk to credential theft and data exfiltration is substantial. The ease of social engineering users to click links makes this a preferred vector for targeted attackers. Organizations should treat this as a priority-one remediation task.

Risk score, explained

The CVSS 3.1 score of 8.8 (HIGH) is justified by: (1) Network attack vector—no local access needed; (2) Low complexity—attacker need only serve a crafted HTML page; (3) No privilege escalation or special conditions required; (4) User interaction required (clicking a link) but readily achievable through social engineering; (5) Isolated scope (renderer sandbox); (6) High impact on confidentiality, integrity, and availability within the renderer context. While the sandbox mitigates complete system compromise, the score correctly reflects the serious risk to user data and session security.

Frequently asked questions