dbcve.org
ChromeWeb browser · Google

CVE-2026-15778

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 150.0.7871.125 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

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 · unedited
Insufficient validation of untrusted input in Navigation in Google Chrome prior to 150.0.7871.125 allowed a remote attacker who had compromised the renderer process to bypass navigation restrictions 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 · moderate confidence

Insufficient validation of untrusted input in Google Chrome's Navigation component prior to version 150.0.7871.125 allowed a remote attacker who had already compromised the renderer process to bypass navigation restrictions via a crafted HTML page. This represents a security boundary bypass where the renderer process can perform unauthorized navigation actions that should be restricted.

MitigationUpdate Google Chrome to version 150.0.7871.125 or later. In enterprise environments, deploy browser update policies to ensure all systems receive the patched version.

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
Affected:< 150.0.7871.125

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Google Chrome is installed
    On Windows, open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" 2>nul. On macOS, run: ls /Applications/ | grep -i chrome. On Linux, run: dpkg -l | grep -i chrome or rpm -q google-chrome.
    Affected if No Chrome installation is found in the system.
  2. Determine installed Chrome version on Windows
    Run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\chrome.exe" /v "(Default)" to get the path, then run: "<path_to_chrome>" --version or navigate to chrome://version in the browser.
    Affected if Cannot retrieve version information.
  3. Determine installed Chrome version on macOS
    Run: defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString
    Affected if Cannot retrieve version information.
  4. Determine installed Chrome version on Linux
    Run: google-chrome --version or /usr/bin/google-chrome --version
    Affected if Cannot retrieve version information.
  5. Compare version against affected range
    Parse the version number obtained and compare it numerically to 150.0.7871.125. Any version less than 150.0.7871.125 (such as 149.x.x.x, 148.x.x.x, etc.) is affected.
    Affected if The installed version is below 150.0.7871.125.

A system is affected if Google Chrome is installed and the installed version number is less than 150.0.7871.125.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 150.0.7871.125 or later
Fixed in 150.0.7871.125
Interim mitigation

Update Google Chrome to version 150.0.7871.125 or later. In enterprise environments, deploy browser update policies to ensure all systems receive the patched version.

Recommended fix High confidence

Chrome 150.0.7871.125 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Verify the current version number displayed
  3. If the version is below 150.0.7871.125, click 'Update Google Chrome' to download and install the latest version
  4. Restart the browser to apply the update
  5. Alternatively, download the latest Chrome version directly from the official Google Chrome website (chrome.com) and reinstall
Caveat Browser upgrades typically have minimal breaking changes; however, some legacy web applications or extensions may experience compatibility issues with newer Chrome versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15778 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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