ChromeWeb browser · Google
CVE-2026-3937
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 · uneditedIncorrect security UI in Downloads in Google Chrome on Android prior to 146.0.7680.71 allowed a remote attacker to perform UI 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 confidenceUI spoofing vulnerability in Google Chrome on Android's Downloads feature. A remote attacker can craft a malicious HTML page to misrepresent the security UI in the Downloads section, potentially tricking users into believing they're interacting with legitimate content when they're not.
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
< 146.0.7680.71CVSS 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.
-
Verify Google Chrome for Android is installedOpen the app drawer or home screen on the Android device and locate the Google Chrome icon. If present, note that Chrome for Android is installed.Affected if Google Chrome for Android is not installed on the device, this CVE does not apply
-
Check installed Chrome versionOpen Google Chrome on the Android device, tap the three-dot menu in the top-right corner, scroll down and select 'Settings', then tap 'About Chrome' to display the current version number.Affected if The displayed version number is less than 146.0.7680.71 (for example, 146.0.7680.70 or lower)
-
Confirm Downloads feature usageThis vulnerability affects the Downloads section in Chrome. Access Chrome settings and verify if the Downloads feature has been used or is accessible by going to the Downloads manager.Affected if The device runs a Chrome version below 146.0.7680.71 AND the user accesses or has accessed the Downloads feature in Chrome
A user is affected if Google Chrome for Android version is lower than 146.0.7680.71 and the Downloads feature is accessible on their device.
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 · scoped146.0.7680.71
Update Google Chrome for Android to version 146.0.7680.71 or later. Users should also be cautious when downloading and interacting with files from untrusted sources.
Chrome 146.0.7680.71 or later on Android
- Open Google Play Store on the Android device
- Search for Google Chrome or locate it in installed apps
- Tap the Update button to install the latest version
- Verify the installed version is 146.0.7680.71 or later via Chrome > Settings > About 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
- 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-3937 — 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-3937 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