ChromeWeb browser · Google
CVE-2026-13809
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 · uneditedSide-channel information leakage in Safe Browsing in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
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 confidenceA side-channel information leakage vulnerability in Safe Browsing on Google Chrome for iOS (versions prior to 150.0.7871.47) allows a remote attacker with a compromised renderer process to leak cross-origin data through a crafted HTML page. This bypasses same-origin policy protections via timing or cache-based side-channel techniques.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 iOS is installedOpen iOS Settings, scroll down to find Google Chrome in the app list. Alternatively, check via MDM or look for the Chrome app icon on the device home screen.Affected if Chrome for iOS is present on the device
-
Locate the installed Chrome version numberIn iOS Settings, tap Google Chrome, then tap Version. Record the displayed version number (e.g., 150.0.7871.45).Affected if Version number is visible and can be compared
-
Compare installed version against vulnerable rangeCompare the recorded version number to 150.0.7871.47. Any version prior to 150.0.7871.47 (such as 149.x.x.x or earlier) is in the vulnerable range.Affected if Installed version is less than 150.0.7871.47
-
Confirm Safe Browsing is enabled (required for exploitation)In iOS Settings, tap Google Chrome, then look for Safe Browsing or Privacy & Security settings. Verify if Safe Browsing protection is turned on.Affected if Safe Browsing is enabled AND version is below 150.0.7871.47
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, as the vulnerability requires the Safe Browsing feature to be active.
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 on iOS to version 150.0.7871.47 or later. For enterprise environments, use MDM to verify and enforce the update across managed devices.
Chrome iOS 150.0.7871.47 or later
- Open the App Store on your iOS device
- Search for Google Chrome or navigate to your installed apps
- Tap on Chrome and select 'Update' if an update is available
- Alternatively, open Chrome, go to Settings > Help & Info > About Chrome to check for and apply updates
- Ensure the updated version is 150.0.7871.47 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13809 — 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-13809 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