CVE-2026-87615

Analyzed Analyzed - Analysis Complete

Race Condition in Google Chrome Payments UI Spoofing

Publication date: 2026-09-09

Last updated on: 2026-09-10

Assigner: Chrome

Description

Race condition in Payments in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-09

Last Modified

2026-09-10

Generated

2026-09-29

AI Q&A

2026-09-10

EPSS Evaluated

2026-09-27

NVD

CVE-2026-87615

EUVD

EUVD-2026-74330

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 153.0.8010.36 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This vulnerability is a race condition in the Payments feature of Google Chrome before version 153.0.8010.36. A race condition occurs when the behavior of a system depends on the sequence or timing of uncontrollable events. In this case, it allows a remote attacker to trick users into seeing fake UI elements by exploiting a timing issue in the browser's payment processing.

Detection Guidance

This vulnerability involves a race condition in Google Chrome's Payments feature, which could allow UI spoofing via crafted HTML. Detection primarily requires checking Chrome version and monitoring for suspicious UI behavior. Update Chrome to version 153.0.8010.36 or later to mitigate the issue.

Impact Analysis

This vulnerability could allow an attacker to deceive you into thinking you are interacting with a legitimate payment interface when you are not. This might lead to unintended transactions, disclosure of sensitive payment information, or other fraudulent activities.

Compliance Impact

This vulnerability involves a race condition in Google Chrome's Payments feature that could allow UI spoofing via a crafted HTML page. While not directly tied to GDPR or HIPAA, such UI spoofing could potentially lead to phishing attacks or unauthorized data disclosure, which may impact compliance by exposing sensitive user data or payment information.

Mitigation Strategies

Update Google Chrome to version 153.0.8010.36 or later to address the race condition in Payments that could allow UI spoofing via crafted HTML pages.

Hi! I’m here to help you understand CVE-2026-87615. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70