0.0
NA
CVE-2026-87595
Google Chrome Server-Side Request Forgery
Description

Server-side request forgery in Mobile in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low)

INFO

Published Date :

Sept. 9, 2026, 1:17 a.m.

Last Modified :

Sept. 9, 2026, 1:17 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-87595 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Google chrome
2 Google chrome
Solution
Update Chrome to patch SSRF vulnerability, preventing malicious HTML pages from bypassing restrictions.
  • Update Google Chrome to version 153.0.8010.36 or later.
  • Educate users about social engineering risks.
  • Implement stricter input validation for URLs.
  • Configure network security to restrict unauthorized requests.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-87595.

URL Resource
https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html
https://issues.chromium.org/issues/513726466
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-87595 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-87595 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-87595 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-87595 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Sep. 09, 2026

    Action Type Old Value New Value
    Added Description Server-side request forgery in Mobile in Google Chrome prior to 153.0.8010.36 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Low)
    Added CWE CWE-918
    Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/87xxx/CVE-2026-87595.json">CVE-2026-87595</a>
    Added Reference https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html
    Added Reference https://issues.chromium.org/issues/513726466
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.