CyberSecBulletin
CVE-2025-6558Exploited in the wildNVD status: Analyzed

Google Chromium ANGLE and GPU Improper Input Validation

Published Updated By the CyberSecBulletin desk

CVE-2025-6558 is a high-severity improper input validation vulnerability in Chrome from Google, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 138.0.7204.157 as the first without the flaw, so updating Chrome to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on July 22, 2025, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Chrome to 138.0.7204.157 or a later version.
  2. Update Safari to 18.6 or a later version.
  3. Update iPadOS to 18.6 or a later version.
  4. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  6. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleChrome138.0.7204.157 up to, but not including, 138.0.7204.157138.0.7204.157
DebianDebian Linux11.0Not stated
AppleSafaribefore 18.618.6
AppleiPadOSbefore 18.618.6
AppleIphone OSbefore 18.618.6
ApplemacOSbefore 15.615.6
AppleVisionosbefore 2.62.6
ApplewatchOSbefore 11.611.6
WpewebkitWpe Webkitbefore 2.48.52.48.5
WebkitgtkWebkitgtkbefore 2.48.52.48.5

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

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)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Chrome

All Chrome vulnerabilities

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.