CVE-2026-84349: High Use after free in Browser

Published Jul 21, 2026
·
Updated

Chromium: CVE-2026-84349 Use after free in Browser

Other sources

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Use after free in Browser in Google Chrome prior to 152.0.7977.75 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)

— MITRE

Credit

Google

Affected Software

4 affected componentsFixes available
Google Google Chrome<152.0.7977.75
Google Chrome<152.0.7977.75
Microsoft Edge (Chromium-based)<152.0.4191.62
152.0.4191.62
Microsoft Edge<152.0.4191.62

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 152.0.4191.62
  2. Upgrade

    Upgrade Google Chrome (Chromium) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.75
  3. Compensating control

    Because the vulnerability requires a compromised renderer process to escape the sandbox, ensure the browser sandboxing model remains enabled and restrict exposure to untrusted HTML content (e.g., do not open untrusted HTML in the browser) until patched.

Event History

Sep 1, 2026
CVE Published
via MITRE·11:42 PM
Data Sourced
via MITRE·11:42 PM
DescriptionWeakness
Sep 2, 2026
Data Sourced
via NVD·12:18 AM
DescriptionSeverityWeaknessAffected Software
Sep 3, 2026
Data Sourced
via Microsoft·11:58 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·11:58 PM
DescriptionAffected Software
Sep 8, 2026
Updated
via Microsoft·02:00 PM
DescriptionAffected Software
Sep 11, 2026
Data Sourced
12:00 AM
SeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What does an attacker need before this flaw can be used to escape the Chrome sandbox?

The attacker must first compromise the Chrome renderer process. After that prerequisite is met, a crafted HTML page can be used to execute arbitrary code outside the sandbox.

2

Which Chrome versions should be remediated?

Google Chrome versions prior to 152.0.7977.75 are affected. Update Chrome to 152.0.7977.75 or a later version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203