ChromeWeb browser · Google
CVE-2026-13904
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 · uneditedInappropriate implementation in Safe Browsing in Google Chrome on iOS prior to 150.0.7871.47 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 · moderate confidenceThis vulnerability in Google Chrome on iOS allowed Safe Browsing restrictions to be bypassed through a crafted HTML page. Safe Browsing is Google's security feature that warns users about potentially malicious websites; this flaw permitted attackers to potentially navigate users to dangerous sites without triggering the expected safety warnings.
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
< 150.0.7871.47CVSS 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.
-
Find the installed Google Chrome version on iOSOpen the Chrome app, tap the three-dot menu, go to Settings, and locate the version number typically shown under 'Chrome' or 'About Chrome'. Alternatively, check in the iOS App Store app listing for Chrome.Affected if The displayed version is lower than 150.0.7871.47
-
Confirm Safe Browsing is enabledIn Chrome settings, navigate to Privacy and Security settings and verify that Safe Browsing protection is turned on. This is typically found under Settings > Privacy and Security or similar path depending on iOS version.Affected if Safe Browsing is toggled to on or enabled in the Chrome settings
-
Verify the bypass condition existsSince this vulnerability allows Safe Browsing warnings to be suppressed when visiting a crafted malicious HTML page, the vulnerability is exploitable whenever Safe Browsing is active and the browser version is vulnerable.Affected if Both conditions are true: Chrome iOS version is below 150.0.7871.47 AND Safe Browsing protection is enabled
A user is affected if Google Chrome for iOS is installed with a version lower than 150.0.7871.47 and Safe Browsing protection is enabled in the browser settings.
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 · scoped150.0.7871.47
Update Google Chrome for iOS to version 150.0.7871.47 or later to obtain the patched version of Safe Browsing.
150.0.7871.47
- Open the App Store on your iOS device
- Search for Google Chrome
- Tap Update to install version 150.0.7871.47 or later
- Alternatively, ensure Chrome auto-update is enabled and wait for automatic installation of the fixed version
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-13904 — 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-13904 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