CVE-2026-91748: Race Condition

Published Sep 15, 2026
·
Updated

Chromium CVE-2026-91748: Race condition

Other sources

Race condition in Extensions in Google Chrome on on Mac prior to 153.0.8010.47 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases](https://chromereleases.googleblog.com/2026)) for more information.

— Microsoft

Affected Software

4 affected componentsFixes available
Google Chrome<153.0.8010.47
All of the following
Google Chrome<153.0.8010.47
Apple macOS
Microsoft Edge (Chromium-based)<153.0.4234.46
153.0.4234.46

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 153.0.4234.46
  2. Upgrade

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

    Fixed in 153.0.8010.47
  3. Compensating control

    On affected Mac systems, mitigate UI-interaction risk by restricting extension/renderer compromise opportunities (e.g., limit/disable untrusted extensions and reduce the chance of renderer-compromising content) until Chrome is updated to 153.0.8010.47 or later.

Event History

Sep 15, 2026
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
DescriptionWeakness
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeaknessAffected Software
Sep 18, 2026
Data Sourced
via Microsoft·04:48 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·04:48 AM
Affected Software
Updated
via Microsoft·04:48 AM
DescriptionSeverity

Frequently Asked Questions

1

Which systems are affected?

The issue affects Google Chrome on Mac versions before 153.0.8010.47. The provided information does not identify impact on other operating systems.

2

What must an attacker do to exploit this issue?

An attacker must first compromise the renderer process and then use social engineering involving UI interaction. Successful exploitation could allow arbitrary code execution outside Chrome's sandbox.

3

Is this exploitable through a renderer compromise alone?

No. The description states that exploitation also requires social engineering and UI interaction after the renderer process has been compromised.

4

What version addresses the issue?

Update Google Chrome on Mac to version 153.0.8010.47 or later.

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