CVE-2026-84350: Use after free in TabStrip

Published May 16, 2026
·
Updated

Chromium: CVE-2026-84350 Use after free in TabStrip

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 TabStrip in Google Chrome prior to 152.0.7977.75 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: Low)

— MITRE

Credit

Google

Affected Software

5 affected componentsFixes available
Google Chrome<152.0.7977.75
Google Chrome<152.0.7977.75
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.7977.75
  2. Upgrade

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

    Fixed in 152.0.4191.62
  3. Upgrade

    Upgrade Chromium (Google Chrome/Edge Chromium-based) to a version that resolves this vulnerability.

    Fixed in 152.0.7977.75Patch CVE-2026-84350

Event History

May 16, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
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:59 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·11:59 PM
DescriptionAffected Software
Sep 8, 2026
Updated
via Microsoft·02:00 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which Chrome releases need to be remediated?

Google Chrome releases prior to 152.0.7977.75 are affected. Update Chrome to 152.0.7977.75 or later.

2

What would an attacker need to exploit this issue?

The attacker must remotely induce user interaction through social engineering. Successful exploitation can result in arbitrary code execution outside the Chrome sandbox.

3

Are systems affected without user involvement?

The available information describes exploitation through UI interaction and social engineering, so user interaction is part of the stated attack scenario.

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