dbcve.org
ChromeWeb browser · Google

CVE-2026-3932

HIGH · 7.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 146.0.7680.71 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 policy enforcement in PDF in Google Chrome on Android prior to 146.0.7680.71 allowed a remote attacker 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 · high confidence

Insufficient policy enforcement in Chrome's PDF viewer on Android allows a remote attacker to bypass navigation restrictions via a crafted HTML page. This could enable malicious PDF content to navigate to arbitrary URLs or perform actions that should be restricted by the browser's security policy.

MitigationUpdate Google Chrome on Android to version 146.0.7680.71 or later. Organizations should ensure mobile device management policies enforce browser updates.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Chrome for Android version
    Open Chrome on the Android device, tap the three-dot menu, go to Settings, then About Chrome to view the current version number
    Affected if The version displayed is lower than 146.0.7680.71
  2. Identify if PDF viewer is accessible
    Attempt to open a PDF file in Chrome on Android or access any web page containing embedded PDF content
    Affected if PDF files can be opened and rendered within the Chrome browser on the Android device
  3. Verify the Android OS version
    Check the Android OS version in Settings > About Phone > Android version
    Affected if The device runs any supported Android version while using a vulnerable Chrome version (the vulnerability affects Chrome regardless of Android version)
  4. Confirm PDF navigation behavior
    If available, test opening a crafted PDF or HTML page with embedded PDF content that attempts unauthorized URL navigation
    Affected if The PDF viewer allows navigation to arbitrary URLs that would be blocked by Chrome's normal security policy

The environment is affected if Google Chrome on Android is installed at any version below 146.0.7680.71 and the browser's PDF viewer feature is used to open PDF files or HTML pages containing PDF content.

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

Update Google Chrome on Android to version 146.0.7680.71 or later. Organizations should ensure mobile device management policies enforce browser updates.

Recommended fix High confidence

Chrome Android 146.0.7680.71 or later

  1. Open the Google Play Store app on your Android device
  2. Search for "Google Chrome" or "Chrome"
  3. Tap on Google Chrome from the search results
  4. If an update is available, tap the "Update" button to install version 146.0.7680.71 or later
  5. Alternatively, ensure your Android device has automatic app updates enabled to receive future security patches
  6. Verify the installed version by opening Chrome, tapping the three dots menu, going to Settings, and checking the Chrome version number

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