Secuno
ENNL
Book demo

CVE-2026-87433

8.8 HIGHEPSS 0.30%
  1. Published8 Sept 2026

Description

Race condition in FileAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionRequired
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Google Chrome< 153.0.8010.36

Remediation

Fixed in
Google Chrome≥ 153.0.8010.36

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-917488.3
Race condition in Extensions in Google Chrome on on Mac prior to 153.0.8010.47 allowed…
CVE-2026-917438.3
Race condition in Core in Google Chrome prior to 153.0.8010.47 allowed a remote…
CVE-2026-917128.3
Race condition in Extensions in Google Chrome on on Mac prior to 153.0.8010.47 allowed…
CVE-2026-400588.8
CrowdStrike released a security update to address a vulnerability in the Falcon sensor…
CVE-2026-875548.1
Race condition in Chromoting in Google Chrome on on Windows prior to 153.0.8010.36…
CVE-2026-874578.1
Race condition in Updater in Google Chrome on on Windows prior to 153.0.8010.36 allowed…

Frequently asked

Is CVE-2026-87433 being actively exploited?

CVE-2026-87433 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.30%.

How severe is CVE-2026-87433?

CVE-2026-87433 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.30% probability of exploitation.

Which products are affected by CVE-2026-87433?

Affected products include Google Chrome.

How do I fix CVE-2026-87433?

Upgrade affected software to a fixed version, for example Google Chrome 153.0.8010.36 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-87433 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.