dbcve.org
ChromeWeb browser · Google

CVE-2026-5905

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
Incorrect security UI in Permissions in Google Chrome on Windows prior to 147.0.7727.55 allowed a remote attacker to perform domain spoofing via a crafted HTML page. (Chromium security severity: Low)

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 confidence

Incorrect security UI in Chrome's Permissions dialog on Windows allowed a remote attacker to perform domain spoofing via a crafted HTML page. The vulnerability was in how the Permissions UI displayed domain information, potentially tricking users into believing they were granting permissions to a different domain than the actual one requesting access.

MitigationUpdate Google Chrome to version 147.0.7727.55 or later. For organizations using Chromium-based browsers, apply the corresponding security patch.

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
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. Verify Chrome is installed on Windows
    Check if Google Chrome exists on the system by looking for chrome.exe in common installation paths such as C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Alternatively, check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome for the presence of a Chrome installation.
    Affected if Chrome is not installed on Windows - this vulnerability only affects Chrome on Windows, so other platforms are not affected by this specific CVE.
  2. Determine the installed Chrome version on Windows
    Open Chrome and navigate to chrome://settings/help, or right-click the Chrome shortcut and select Properties, then look at the Details tab for the Product version. Alternatively, run the command 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version' in Command Prompt to read the version from the registry.
    Affected if The version cannot be determined - you need a readable version number to assess vulnerability status.
  3. Compare installed version against affected range
    Take the version number obtained from the previous step (for example, 147.0.7727.55) and compare it numerically to the affected threshold 147.0.7727.55. Any version lower than 147.0.7727.55 is affected; versions equal to or higher than 147.0.7727.55 are not affected.
    Affected if The installed version is less than 147.0.7727.55 - for example, versions like 147.0.7727.0, 146.0.6498.127, or any earlier release are vulnerable to the permissions dialog domain spoofing.

A user is affected if Google Chrome is installed on Windows and the installed version is lower than 147.0.7727.55, as this UI spoofing flaw in the permissions dialog only impacts those specific older versions on the Windows platform.

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. For organizations using Chromium-based browsers, apply the corresponding security patch.

Recommended fix High confidence

Chrome 147.0.7727.55

  1. 1. Open Google Chrome on the Windows system
  2. 2. Navigate to Chrome menu > Help > About Google Chrome
  3. 3. Chrome will check for updates automatically
  4. 4. If an update is available, click 'Update Google Chrome'
  5. 5. Wait for the download to complete and click 'Relaunch' to restart the browser
  6. 6. Verify the version by returning to Help > About Google Chrome and confirm the version is 147.0.7727.55 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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5905 — 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-5905 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