Secuno
ENNL
Book demo

CVE-2026-87457

8.1 HIGHEPSS 0.08%
  1. Published8 Sept 2026

Description

Race condition in Updater in Google Chrome on on Windows prior to 153.0.8010.36 allowed a local attacker to execute arbitrary code outside the sandbox via a local program. (Chromium security severity: Medium)

CVSS 3.1 breakdown

Attack vectorLocal
Attack complexityHigh
Privileges requiredNone
User interactionNone
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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-874338.8
Race condition in FileAPI in Google Chrome prior to 153.0.8010.36 allowed a remote…

Frequently asked

Is CVE-2026-87457 being actively exploited?

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

How severe is CVE-2026-87457?

CVE-2026-87457 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.08% probability of exploitation.

Which products are affected by CVE-2026-87457?

Affected products include Google Chrome.

How do I fix CVE-2026-87457?

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-87457 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.