Skip to main content

CVE-2026-130928Google Chrome code injection

Low priorityNot scoredEPSS not scored yet

CVE-2026-130928 is a code injection 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

Input is evaluated as code by the application, so an attacker's code runs inside it.

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 run commands or code with the privileges of the affected service.

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

Code injection in Mobile in Google Chrome on on Android prior to 158.0.8127.36 allowed a local attacker leveraging social engineering to bypass web origin policy 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

  • Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
  • Template engines. The flaw sits between untrusted input and code or command execution.

Trust boundaries in play

  • Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.

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.