ChromeWeb browser · Google
CVE-2026-5858
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 · uneditedHeap buffer overflow in WebML in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)
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 confidenceHeap buffer overflow vulnerability in Chrome's WebML (Web Machine Learning) component allows remote code execution via a maliciously crafted HTML page. The flaw exists in versions prior to 147.0.7727.55.
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
- 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.
-
Determine if Google Chrome is installedOpen chrome://settings/help or run 'google-chrome --version' in terminal to check if Chrome is present on the systemAffected if Google Chrome is not installed - this CVE does not apply
-
Check installed Chrome versionNavigate to chrome://version in the Chrome browser address bar or run 'google-chrome --version' via command line. Note the full version number displayed.Affected if The version shown is less than 147.0.7727.55 - the vulnerable version is present
-
Verify if WebML feature is enabledNavigate to chrome://flags/#webml in the Chrome address bar and check the WebML setting statusAffected if WebML is set to Enabled - the vulnerable component is active; if set to Disabled, the attack surface may be reduced
-
Confirm browser is used in a context where malicious HTML could be loadedReview whether the Chrome browser profile can load arbitrary web pages or is restricted via enterprise policies, parental controls, or kiosk modeAffected if Browser can load arbitrary HTML pages from untrusted sources - necessary condition for remote exploitation
User is affected if Chrome version is below 147.0.7727.55 AND WebML feature is enabled AND the browser can load untrusted web content
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. In enterprise environments, deploy the update via standard endpoint management tools and verify compliance.
Chrome 147.0.7727.55 or later
- 1. Open Google Chrome on your device
- 2. Click the three-dot menu in the top-right corner
- 3. Select 'Help' and then 'About Google Chrome'
- 4. Chrome will automatically check for updates
- 5. If version 147.0.7727.55 or later is available, click 'Update Google Chrome'
- 6. Restart the browser to apply the update
- 7. Verify the update by returning to Help > About Google Chrome and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5858 — 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-5858 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