ChromeWeb browser · Google
CVE-2026-15776
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 150.0.7871.125 allowed a remote attacker to execute arbitrary code inside a sandbox 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 · moderate confidenceV8 JavaScript engine vulnerability in Google Chrome prior to version 150.0.7871.125 allows a remote attacker to achieve arbitrary code execution inside the sandbox through a specially crafted HTML page. This represents an inappropriate implementation flaw in Chrome's V8 engine.
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
< 150.0.7871.125CVSS 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 installed Chrome versionOpen chrome://version in the address bar or run 'google-chrome --version' (Linux/macOS) or 'chrome --version' (Windows) in terminal/command promptAffected if version number shown is less than 150.0.7871.125
-
Confirm Chrome is using V8 engineNavigate to chrome://version and locate the V8 version field in the output, or visit a site like chrome://gpu to view JavaScript engine detailsAffected if V8 engine is present and its version matches the Chrome version (V8 is built into all standard Chrome installations)
-
Check if outdated Chrome is in active useReview all Chrome installations on the system (including browser-based profiles, enterprise deployments, or alternate channels like Beta/Dev/Canary) using 'chrome://settings/help'Affected if Any active Chrome installation shows a version below 150.0.7871.125
You are affected if any Chrome installation in use has a version number lower than 150.0.7871.125, as this indicates the vulnerable V8 engine version is present.
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 · scoped150.0.7871.125
Update Google Chrome to version 150.0.7871.125 or later to patch the V8 vulnerability. Users should also ensure automatic updates are enabled.
Chrome 150.0.7871.125 or later
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- The browser will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- After the update installs, click 'Relaunch' to restart the browser and apply the changes
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15776 — 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-15776 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