ChromeWeb browser · Google
CVE-2025-5419
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 · uneditedOut of bounds read and write in V8 in Google Chrome prior to 137.0.7151.68 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 confidenceA memory safety vulnerability in the V8 JavaScript engine in Google Chrome allows a remote attacker to perform out-of-bounds read and write operations via a maliciously crafted HTML page, potentially leading to heap corruption and arbitrary code execution.
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
< 137.0.7151.68< 137.0.3296.62CVSS 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.
-
Identify browser vendor and versionOpen Chrome or Edge, click the three-dot menu, select 'Help' then 'About Google Chrome' or 'About Microsoft Edge'. Note the version number displayed.Affected if The browser version is Google Chrome < 137.0.7151.68 or Microsoft Edge (Chromium) < 137.0.3296.62
-
Confirm JavaScript is enabledIn Chrome: Settings > Privacy and security > Site settings > JavaScript. In Edge: Settings > Cookies and site permissions > JavaScript. Verify JavaScript is allowed for general use.Affected if JavaScript is enabled (this is required for the V8 engine vulnerability to be exploitable)
-
Check for recent browser usage with untrusted web contentReview browser history or logs for visits to untrusted or unfamiliar websites around the time of potential exposure. This helps determine if the system may have been targeted.Affected if The browser has been used to visit potentially malicious web pages that could contain specially crafted HTML designed to trigger the V8 vulnerability
You are affected if you are running Google Chrome version below 137.0.7151.68 or Microsoft Edge (Chromium) version below 137.0.3296.62, and JavaScript is enabled in the browser settings.
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 · scoped137.0.3296.62137.0.7151.68
Update Google Chrome to version 137.0.7151.68 or later to remediate this vulnerability.
Chrome 137.0.7151.68+ / Edge Chromium 137.0.3296.62+
- For Google Chrome: Navigate to Settings > Help > About Google Chrome, then click 'Update Google Chrome' to install version 137.0.7151.68 or later
- For Microsoft Edge: Navigate to Settings > About Microsoft Edge to check for and install version 137.0.3296.62 or later
- Restart the browser after the update completes
- Verify the installed version by returning to the About page and confirming it shows 137.0.7151.68 or higher for Chrome, or 137.0.3296.62 or higher for Edge
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
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 locallyCheck whether your project pulls in CVE-2025-5419 — 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-5419 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