ChromeWeb browser · Google
CVE-2026-0902
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 · uneditedInappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)
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 vulnerability in the V8 JavaScript engine of Google Chrome prior to version 144.0.7559.59 allows a remote attacker to perform an out-of-bounds memory read via a crafted HTML page. This improper implementation in V8 can expose sensitive memory contents to an attacker.
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
< 144.0.7559.59< 144.0.7559.60CVSS 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.
-
Verify Google Chrome is installedOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' in terminalAffected if Google Chrome is not installed - the system is not affected by this specific Chrome vulnerability
-
Identify installed Chrome versionOn Chrome, go to chrome://settings/help to see the version number displayed under 'Google Chrome'. From command line, run 'google-chrome --version' or check the application propertiesAffected if Version cannot be determined - assume potentially affected if Chrome is present
-
Compare version against affected rangeCompare the installed version number to the affected range: versions prior to 144.0.7559.59 (or 144.0.7559.60) are vulnerable. The first three version number segments (144.0.7559) must be compared, then the final segment (59 or 60)Affected if Installed version is less than 144.0.7559.59 - the environment is affected and the V8 out-of-bounds read vulnerability is present
A user is affected if Google Chrome is installed and the installed version is lower than 144.0.7559.59 (or 144.0.7559.60 depending on the specific patch channel).
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 · scoped144.0.7559.59144.0.7559.60
Update Google Chrome to version 144.0.7559.59 or later to patch the vulnerable V8 implementation.
Chrome version 144.0.7559.59 or later (or 144.0.7559.60 for affected channel)
- Open Google Chrome on your system
- Navigate to Chrome menu > Help > About Google Chrome
- Click 'Check for updates' or wait for automatic update check
- If version is below 144.0.7559.59, download and install the latest version from chrome.com/get-chrome or the official repository for your platform
- Restart Chrome after the update completes
- Verify the installed version by returning to Help > About Google Chrome and confirming it shows 144.0.7559.59 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0902 — 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-2026-0902 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