ChromeWeb browser · Google
CVE-2026-15775
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 bypass same origin policy 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 vulnerability in Google Chrome's V8 JavaScript engine (prior to version 150.0.7871.125) allowed remote attackers to bypass the same origin policy via a crafted HTML page. This security flaw enabled scripts from one origin to access resources from a different origin, violating a fundamental browser security mechanism.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://version, or go to Settings > About Chrome. The version number is displayed at the top of the page.Affected if The displayed version number is less than 150.0.7871.125
-
Verify JavaScript is enabledNavigate to chrome://settings/content/javascript. Ensure JavaScript is allowed (toggle is ON).Affected if JavaScript is enabled - this vulnerability exploits the V8 JavaScript engine, so JS must be active for the attack to function.
-
Check for pending updatesNavigate to chrome://settings/help. The page will either show 'Chrome is up to date' or indicate an available update.Affected if An update is available and the current version is below 150.0.7871.125, meaning the browser is running a vulnerable version.
The environment is affected if Google Chrome is running a version prior to 150.0.7871.125 and JavaScript is enabled, allowing a crafted webpage to exploit the V8 same-origin policy bypass.
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. For enterprise environments, deploy the update through standard patch management processes and verify the update has been applied.
Chrome 150.0.7871.125 or later
- Open Google Chrome browser
- Click on the Chrome menu (three dots) in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- The browser will automatically check for and install updates
- Once update is complete, click 'Relaunch' or restart the browser manually
- After restarting, return to 'About Google Chrome' to verify the version number is 150.0.7871.125 or later
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-15775 — 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-15775 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