dbcve.org
ChromeWeb browser · Google

CVE-2026-0903

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-20
Fix available
A fix is available. Upgrade to 144.0.7559.59 / 144.0.7559.60 or later.
See remediation →
61/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
Inappropriate implementation in Downloads in Google Chrome on Windows prior to 144.0.7559.59 allowed a remote attacker to bypass dangerous file type protections via a malicious file. (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 · high confidence

This vulnerability in Google Chrome on Windows (versions prior to 144.0.7559.59) involves an implementation flaw in the Downloads component that allows a remote attacker to bypass dangerous file type protection mechanisms. By crafting a malicious file, an attacker could trick the browser into downloading file types that should be blocked by Chrome's safe browsing or download protection features.

MitigationUpdate Google Chrome to version 144.0.7559.59 or later on all Windows systems to address the improper download protection bypass.

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:< 144.0.7559.59< 144.0.7559.60

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 Google Chrome is installed on Windows
    Open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v DisplayName 2>nul || reg query "HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v DisplayName 2>nul
    Affected if Chrome is not found in the registry, indicating it may not be installed or is installed elsewhere
  2. Check installed Chrome version on Windows
    Launch Chrome, click the three-dot menu, select Help > About Google Chrome, or run: chrome --version in Command Prompt
    Affected if The displayed version is earlier than 144.0.7559.59 (or 144.0.7559.60 depending on the specific patch applied)
  3. Confirm Windows platform
    Run: ver in Command Prompt or check System Properties - this vulnerability specifically affects Chrome on Windows
    Affected if The system is running any version of Windows and Chrome version is below 144.0.7559.59
  4. Verify Downloads component is in use
    Check if Chrome has download functionality enabled by navigating to chrome://settings/downloads or inspecting downloaded files history at %USERPROFILE%\Downloads
    Affected if Downloads feature is active and Chrome version is vulnerable, the bypass could be exploited

A user is affected if Google Chrome on Windows is installed with a version lower than 144.0.7559.59 (or 144.0.7559.60), enabling the dangerous file type protection bypass in the Downloads 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 144.0.7559.59 / 144.0.7559.60 or later
Fixed in 144.0.7559.59144.0.7559.60
Interim mitigation

Update Google Chrome to version 144.0.7559.59 or later on all Windows systems to address the improper download protection bypass.

Recommended fix High confidence

Chrome 144.0.7559.59 or later (stable channel)

  1. Open Google Chrome and navigate to Settings by clicking the three-dot menu in the top-right corner
  2. Scroll down and click 'About Chrome' in the left sidebar
  3. Chrome will automatically check for updates; if version 144.0.7559.59 or later is available, click 'Update Google Chrome'
  4. Restart the browser to complete the installation
  5. Alternatively, on Windows, you can update via the system's Google Chrome update notification if one appears
Caveat Chrome stable updates typically have no breaking changes for end users; extensions and settings are preserved

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