dbcve.org
ChromeWeb browser · Google

CVE-2026-5876

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 147.0.7727.55 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Side-channel information leakage in Navigation in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to leak cross-origin data 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

A side-channel information leakage vulnerability in Google Chrome's navigation mechanism allowed a remote attacker to leak cross-origin data via a crafted HTML page. The flaw exploited timing or other side-channel signals during browser navigation to bypass same-origin policy protections and access sensitive data from other origins.

MitigationUpdate Google Chrome to version 147.0.7727.55 or later to remediate this vulnerability. Users should be instructed to update their browsers or organizations should deploy updates via enterprise management tools.

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:< 147.0.7727.55

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Confirm Google Chrome is in use
    Check if Google Chrome is installed by looking for chrome.exe on Windows (typically in Program Files\Google\Chrome\Application\) or chrome on macOS/Linux (typically in /Applications/Google Chrome.app or /usr/bin/google-chrome)
    Affected if Google Chrome is installed and being used as the browser
  2. Retrieve the installed Chrome version
    Open Chrome, click the three-dot menu, select Help, then About Google Chrome. Alternatively, navigate to chrome://settings/help in the address bar. The version number is displayed at the top of the page.
    Affected if Cannot retrieve version or Chrome is not accessible for version check
  3. Compare version to the affected range
    Note the version number displayed (format typically shows three number groups like X.X.X.X). Compare the installed version against 147.0.7727.55 using standard version comparison rules.
    Affected if The installed version is less than 147.0.7727.55 (for example, 147.0.7727.0, 146.0.1234.56, or any earlier version)
  4. Verify the Chrome channel (optional)
    In chrome://settings/help, also check if the browser shows as Stable, Beta, Dev, or Canary channel. This confirms whether updates are being applied from the standard release track.
    Affected if Chrome is on Stable channel but reports a version below 147.0.7727.55, indicating the security update has not been applied

The environment is affected if Google Chrome is installed and the displayed version is numerically lower than 147.0.7727.55, meaning the browser is vulnerable to the cross-origin data leakage side-channel attack in the Navigation component.

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 147.0.7727.55 or later
Fixed in 147.0.7727.55
Interim mitigation

Update Google Chrome to version 147.0.7727.55 or later to remediate this vulnerability. Users should be instructed to update their browsers or organizations should deploy updates via enterprise management tools.

Recommended fix High confidence

Chrome 147.0.7727.55 or later

  1. Open Google Chrome and navigate to Chrome menu > Help > About Google Chrome
  2. Verify the current version. If it is below 147.0.7727.55, Chrome will automatically check for updates
  3. Click 'Update Google Chrome' if an update is available
  4. Restart the browser to complete the installation
  5. Confirm the version is now 147.0.7727.55 or later in About Google Chrome

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-5876 — 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-5876 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