ChromeWeb browser · Google
CVE-2026-3930
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 · uneditedUnsafe navigation in Navigation in Google Chrome on iOS 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 confidenceUnsafe navigation in Google Chrome on iOS allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. This could enable malicious pages to perform unauthorized navigation actions that should normally be blocked by the browser's security model.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installed on iOSOn the iOS device, locate the Chrome app icon on the home screen or in the app library. Confirm the Google Chrome browser for iOS is present.Affected if Google Chrome on iOS is not installed
-
Check installed Chrome version on iOSOpen Chrome, tap Settings (three dots or menu icon), scroll to the top where 'Chrome' displays the version number (e.g., 146.0.7680.x), or navigate to chrome://version in the address bar to see the full version string.Affected if Unable to retrieve version information from Chrome on iOS
-
Compare the installed version number to the affected range: versions prior to 146.0.7680.71 are vulnerable. For example, 146.0.7680.70 is affected, 146.0.7680.71 or later is not.Affected if Installed version is lower than 146.0.7680.71 (e.g., 146.0.7680.70, 145.x.x.x, etc.)
A user is affected if Google Chrome on iOS is installed with a version number lower than 146.0.7680.71.
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 on iOS to version 146.0.7680.71 or later to remediate this vulnerability. Organizations should ensure managed iOS devices have the latest Chrome update applied.
Chrome iOS 146.0.7680.71 or later
- Open the App Store on the iOS device
- Search for 'Google Chrome' or locate it in your installed apps
- Check for available updates - look for version 146.0.7680.71 or later
- Tap update to install the latest version
- Alternatively, go to App Store Settings > Automatic Updates and enable automatic updates to ensure future security patches are applied automatically
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-3930 — 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-3930 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