Skip to main content

CVE-2026-130932Google Chrome resource exposed to the wrong sphere

Low priorityNot scoredEPSS not scored yet

CVE-2026-130932 is a resource exposed to the wrong sphere in Google Chrome, not yet scored.

Why this priority: Not scored yet, and no exploitation signal.

Published · Updated · NVD status: Awaiting Analysis

What it is

A resource is reachable by parties outside the ones it was meant for.

How it is reached

The record does not say yet how the flaw is reached; the description below is the best guide until it is scored.

What an attacker gains

Its impact has not been scored yet. In practice, this kind of flaw lets an attacker learn data or internals that help a follow-up attack.

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.

Description from NVD

Improper resource exposure in Core in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)

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

  • Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
  • APIs that over-share. The flaw sits between internal data and whoever can read the response or log.

Trust boundaries in play

  • Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.

Questions to answer about your own systems

  • Where does Google Chrome run in your systems, and at which version?
  • Which of those instances are reachable by people you do not 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.