Skip to main content

CVE-2026-131032Google Chrome unintended proxy

Low priorityMedium5.1EPSS not scored yet

CVE-2026-131032 is a unintended proxy in Google Chrome, rated medium (5.1 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Awaiting Analysis

What it is

The server can be made to relay requests to places the attacker cannot reach directly.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker make the server send requests into internal networks or cloud metadata.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade Google Chrome to 158.0.8127.36 or later.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Confused deputy in UI in Google Chrome on on Android prior to 158.0.8127.36 allowed a local attacker leveraging social engineering to obtain sensitive information via a co-installed app. (Chromium security severity: Medium)

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.

Questions to answer about your own systems

  • Where does Google Chrome run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.