ChromeWeb browser · Google
CVE-2025-7657
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 · uneditedUse after free in WebRTC in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially exploit heap corruption 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 confidenceThis is a use-after-free vulnerability in Google's WebRTC (Web Real-Time Communication) component. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption and arbitrary code execution. The vulnerability affects Chrome versions prior to 138.0.7204.157.
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
< 138.0.7204.157CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Google Chrome is installedOn Windows, look for Chrome in Program Files (x86)\Google\Chrome\Application\ or check via Control Panel > Programs and Features. On macOS, check /Applications for Google Chrome.app. On Linux, run 'which google-chrome' or check package manager listings.Affected if Google Chrome browser is present on the system
-
Identify installed Chrome versionOpen Chrome and navigate to chrome://version in the address bar, or right-click the Chrome shortcut and select 'Properties' then look at the 'Details' tab. On Linux/macOS, run 'google-chrome --version' in terminal.Affected if Chrome version cannot be determined or is lower than 138.0.7204.157
-
Compare version against affected rangeThe installed version number (such as 138.0.7204.156 or any 137.x.x.x release) must be compared numerically to 138.0.7204.157. Any version below this threshold is within the affected range.Affected if Installed version is 138.0.7204.156 or lower, or any 137.x.x.x, 136.x.x.x, or earlier major version
If Chrome is installed and its version number is less than 138.0.7204.157, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped138.0.7204.157
Update Google Chrome to version 138.0.7204.157 or later. Organizations should deploy the update via their standard patch management processes (GPO, MDM, or enterprise update channels).
138.0.7204.157
- Open Google Chrome and navigate to chrome://settings/help to check for updates
- If an update is available, Chrome will automatically download it or present an 'Update Google Chrome' button - click it to initiate the update
- After the update completes, restart Google Chrome to apply the changes
- Once Chrome restarts, return to chrome://settings/help to confirm the version number is 138.0.7204.157 or later, confirming the security patch is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7657 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-7657 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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