Skip to main content
veriom
Menu

Explore Veriom products, resources, and account pages.

CVE-2025-6558Google Chromium ANGLE and GPU Improper Input Validation Vulnerability

Patch nowHigh8.8Exploited, CISA due date 2025-08-12EPSS 11%, higher than 96% of scored CVEs

CVE-2025-6558 is a improper input validation in Google Chromium, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

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

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2025-07-22: it is being exploited in the wild. EPSS estimates a 11% chance of exploitation activity in the next 30 days, higher than 96% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2025-08-12.
  2. No fixed version is listed for Google Chromium itself; fixed versions for the other affected products are listed on this page.
  3. Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Warn the people who use it, and filter files and links on the way in.
  5. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

Insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially perform a sandbox escape 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

  • Operating systems on servers, workstations or devices. Everything on the host inherits the flaw.
  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • 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 Chromium run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?
See how Veriom maps an architectureTake the interactive tour

Read more

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.