Skip to main content

CVE-2026-131029Google Chrome improper input validation

Low priorityNot scoredEPSS not scored yet

CVE-2026-131029 is a improper input validation 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

The software trusts input it should check, so crafted values reach code that assumes they are well formed.

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 drive the component into behaviour its authors did not intend.

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 input validation in Extensions in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy into a privileged page via a crafted Chrome extension. (Chromium security severity: Low)

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

  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.

Trust boundaries in play

  • At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.

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.