LiveActive security incident?Get immediate response
CVE Record

CVE-2025-6558: Insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 allowe...

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)

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-6558 is a high-severity Chrome flaw in ANGLE and GPU input validation. A remote attacker could use a crafted HTML page to potentially escape the browser sandbox. CISA lists it as known exploited, so this is not a theoretical issue.

Executive priority

Treat this as an urgent browser patching item. Confirmed exploitation and sandbox escape potential make delayed remediation materially risky for workstation compromise paths, even though user interaction is required.

Technical view

The CVE describes CWE-20 insufficient validation of untrusted input in Google Chrome before 138.0.7204.157. The attack vector is network-based with required user interaction. CVSS 3.1 is 8.8 with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on endpoints running Google Chrome before 138.0.7204.157, especially where browser updates are delayed or user-managed. Evidence in the bundle does not establish other affected products beyond the cited Chrome and vendor package advisories.

Exploitation context

Active exploitation is supported by the CISA Known Exploited Vulnerabilities listing. Public sources describe potential sandbox escape through crafted HTML, but the bundle does not provide exploit mechanics, target scope, or campaign details.

Researcher notes

The available evidence identifies insufficient input validation in ANGLE and GPU with possible sandbox escape from crafted HTML. Public details are limited; avoid assuming exploit chain specifics, affected downstream browsers, or mitigations beyond vendor updates and advisories.

Mitigation direction

  • Update Google Chrome to 138.0.7204.157 or later where applicable.
  • Prioritize internet-facing and high-risk user endpoints for browser update enforcement.
  • Review Debian or other vendor advisories for packaged browser update guidance.
  • Use enterprise browser management to prevent rollback or stalled updates.
  • Check vendor guidance if Chrome cannot be updated immediately.

Validation and detection

  • Inventory Chrome versions across managed endpoints.
  • Confirm installed versions are 138.0.7204.157 or later.
  • Review browser update policy compliance and failure reports.
  • Check vulnerability scanner results for CVE-2025-6558.
  • Track CISA KEV remediation status for applicable assets.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-6558 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-6558Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome138.0.7204.157Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.