ChromeWeb browser · Google
CVE-2026-13913
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 · uneditedInsufficient policy enforcement in Autofill in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to leak cross-origin data 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 confidenceThis vulnerability exists in Google Chrome on iOS versions prior to 150.0.7871.47, where insufficient policy enforcement in the Autofill feature allows a remote attacker to leak cross-origin data. An attacker tricks users into performing specific UI gestures on a crafted HTML page to access autofill data from other origins.
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.
-
Identify Google Chrome on iOSOpen the Chrome app on your iOS device and confirm it is the Google Chrome browserAffected if Google Chrome iOS app is installed and running
-
Locate the installed version numberIn the Chrome app, tap the menu icon (three dots), go to Settings, then look for About Chrome or Chrome version to view the current build numberAffected if Chrome version number is displayed in the app
-
Compare version to the affected rangeCompare the displayed version number to 150.0.7871.47 - the version must be less than this to be vulnerableAffected if Installed version is lower than 150.0.7871.47 (for example, 150.0.7871.40 or any earlier version)
-
Determine if Autofill is in useCheck if Autofill is enabled in Chrome settings under Passwords and Autofill or if you have previously saved form data such as addresses, credit cards, or personal informationAffected if Autofill functionality is enabled or form data has been saved for automatic filling
You are affected if you are running Google Chrome on iOS with a version lower than 150.0.7871.47 and have Autofill enabled or have stored form data that could be accessed.
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 to remediate this vulnerability. Users should avoid interacting with untrusted HTML pages while using autofill functionality.
Chrome iOS 150.0.7871.47 or later
- Open the App Store on your iOS device
- Search for Google Chrome or locate it in your installed apps
- Update Google Chrome to version 150.0.7871.47 or later
- Alternatively, ensure automatic updates are enabled for Chrome in iOS Settings > App Store > Automatic Downloads
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-13913 — 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-13913 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