Cyber Resilience

CVE-2025-6558

Google Chrome ≤ 138.0.7204.157

CISA KEVActive ExploitationEUVD Exploited
Published
15 July 2025
Modified
17 June 2026
KEV Added
22 July 2025
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.092 95th percentile
Risk Priority 90 floored blend · peak EPSS

Summary

CVE-2025-6558 is a high-severity Improper Input Validation (CWE-20) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 5% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Insufficient validation of untrusted input in ANGLE and the GPU component of Google Chrome prior to version 138.0.7204.157 permits a remote attacker to potentially escape the browser sandbox. The flaw is tracked as CVE-2025-6558, carries a CVSS 3.1 score of 8.8, and is assigned CWE-20; Chromium rates the issue High severity.

An attacker who can persuade a user to visit a specially crafted HTML page can trigger the flaw, achieving high impact on confidentiality, integrity, and availability by escaping the renderer sandbox. No user interaction beyond loading the page is required, and the attack can be delivered over the network without authentication.

The stable-channel update released on 15 July 2025 upgrades Chrome to 138.0.7204.157 and addresses the issue; administrators should apply the update promptly. Public references include the Chromium bug tracker entry 427162086 and the corresponding Chrome release announcement. The current EPSS score remains low at 0.0033 with no reported real-world exploitation.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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)

CWE(s)
CWE-20
KEV Date Added
22 July 2025

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1036.001 Invalid Code Signature Stealth
Adversaries may attempt to mimic features of valid code signatures to increase the chance of deceiving a user, analyst, or tool.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-43342Same product: Apple Ipados
CVE-2024-23263Same product: Apple Ipados
CVE-2023-41061Same product: Apple Ipadosboth on KEV
CVE-2022-2856Same product: Apple Macosboth on KEV
CVE-2022-3075Same product: Google Chromeboth on KEV
CVE-2018-7600Same product: Debian Debian Linuxboth on KEV
CVE-2025-31215Same product: Apple Ipados
CVE-2025-31217Same product: Apple Ipados
CVE-2020-0041Same vendor: Googleboth on KEV
CVE-2025-43494Same product: Apple Ipados

Affected Assets

google
chrome
≤ 138.0.7204.157
debian
debian linux
11.0
apple
safari
≤ 18.6
apple
ipados
≤ 18.6
apple
iphone os
≤ 18.6
apple
macos
≤ 15.6
apple
visionos
≤ 2.6
apple
watchos
≤ 11.6
wpewebkit
wpe webkit
≤ 2.48.0
webkitgtk
webkitgtk
≤ 2.48.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing input validation through analysis or test cases.

SI-10 Information Input Validation good match

SI-10 directly requires validity checks on information inputs, structurally preventing improper or missing validation.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can embed input-validation practices into the engineering process.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require and enforce input validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

A.8.26 Application security requirements partial match
prevents

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

A.8.28 Secure coding partial match
prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

A.8.7 Protection against malware none match
none

Regular automated validation of system software and data content, combined with scanning of all inbound files, enforces input validation at the boundary before untrusted content is processed.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

RHEL 8 (1 rule)
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-20

References