dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 12 Aug 2025.
ChromeWeb browser · Google

CVE-2025-6558

HIGH · 8.8 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to 2.6 / 11.6 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Insufficient validation of untrusted input in Chrome's ANGLE (graphics engine abstraction layer) and GPU components allows a remote attacker to execute a crafted HTML page that can potentially escape the browser's sandbox, leading to code execution outside the browser's security boundary.

MitigationUpdate Google Chrome to version 138.0.7204.157 or later to patch this vulnerability. In enterprise environments, ensure the update is deployed across all affected systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 138.0.7204.157
Debian LinuxOperating system
Affected:= 11.0
SafariWeb browser
Affected:< 18.6
IpadosOperating system
Affected:< 18.6
Iphone OsOperating system
Affected:< 18.6
macOSOperating system
Affected:< 15.6
VisionosOperating system
Affected:< 2.6
WatchosOperating system
Affected:< 11.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version on Windows, macOS, or Linux
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://settings/help
    Affected if The displayed version is older than 138.0.7204.157
  2. Check Safari version on macOS
    Open Safari, go to Safari > About Safari, or check /Applications/Safari.app/Contents/Info.plist for CFBundleShortVersionString
    Affected if The displayed version is older than 18.6
  3. Check iOS Safari version on iPhone or iPad
    Go to Settings > Safari > About, or check the iOS version under Settings > General > About
    Affected if The Safari version shown is older than 18.6
  4. Verify iOS/iPadOS version
    Go to Settings > General > About on the iOS device and note the version number
    Affected if The iOS version is older than 18.6
  5. Verify macOS version
    Go to Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if The macOS version is older than 15.6

A user is affected if they run any of these browsers (Chrome, Safari) on versions below the specified thresholds, since the vulnerability requires the browser to be present and enabled to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6 / 11.6 / 15.6 or later
Fixed in 2.611.615.6
Interim mitigation

Update Google Chrome to version 138.0.7204.157 or later to patch this vulnerability. In enterprise environments, ensure the update is deployed across all affected systems.

Recommended fix High confidence

Chrome 138.0.7204.157 (or Safari 18.6, macOS 15.6, iOS/iPadOS 18.6, visionOS 2.6, watchOS 11.6 depending on platform)

  1. For Chrome/Chromium-based browsers: Update to version 138.0.7204.157 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome'
  2. For Safari on macOS: Update to macOS 15.6 or later via System Settings > Software Update
  3. For Safari on iOS/iPadOS: Update to iOS/iPadOS 18.6 or later via Settings > General > Software Update
  4. For Apple devices (visionOS, watchOS): Update to visionOS 2.6, watchOS 11.6 or later via respective Settings > Software Update
  5. For Debian Linux 11.0: Check for and apply Chrome browser updates from Google's official repository or switch to a browser receiving security updates
Caveat Browser updates typically have minimal breaking changes for end users; however, some legacy web features or extensions may be affected

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-6558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-6558 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data