ChromeWeb browser · Google
CVE-2026-5893
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 · uneditedRace in V8 in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to potentially exploit heap corruption 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 confidenceRace condition in V8 (Google's JavaScript engine) in Google Chrome prior to version 147.0.7727.55 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability stems from improper synchronization in V8's handling of concurrent operations, enabling memory corruption that could be triggered by malicious JavaScript code embedded in an HTML page.
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
< 147.0.7727.55CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
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.
-
Check Google Chrome versionNavigate to chrome://settings/help in Chrome browser, or use 'Help > About Google Chrome' menu to view the installed version numberAffected if The displayed version is older than 147.0.7727.55 (e.g., 147.0.7727.54 or any earlier version)
-
Check Chromium-based browser versionFor browsers based on Chromium (Microsoft Edge, Brave, Opera, etc.), check their version through the browser's 'About' menu (usually in Help or Settings > About)Affected if The browser version is based on Chromium prior to the 147.0.7727.55 security update
-
Verify V8 JavaScript engine is in useThe V8 engine is built into Chrome and Chromium-based browsers by default; no manual verification needed for standard installationsAffected if This is always true for Chrome and Chromium-based browsers - the vulnerability exists in the V8 engine component itself
A user is affected if they are running any version of Google Chrome or a Chromium-based browser that is older than version 147.0.7727.55, since the race condition exists in the V8 JavaScript engine of those versions.
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 · scoped147.0.7727.55
Update Google Chrome to version 147.0.7727.55 or later to patch the V8 race condition. Organizations should prioritize updating browser instances that process untrusted web content.
Chrome 147.0.7727.55 or later
- Open Chrome and navigate to chrome://settings/help to check the current version
- Download Chrome version 147.0.7727.55 or later from the official Chrome download page
- Install the updated Chrome version
- Restart Chrome browser to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5893 — 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-5893 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