dbcve.org
ChromeWeb browser · Google

CVE-2026-13889

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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
Side-channel information leakage in WebAuthentication in Google Chrome on iOS prior to 150.0.7871.47 allowed a remote attacker 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 confidence

Side-channel information leakage vulnerability in WebAuthentication API in Google Chrome on iOS prior to version 150.0.7871.47 allows a remote attacker to leak cross-origin data via a crafted HTML page through a side-channel attack.

MitigationUpdate Google Chrome on iOS to version 150.0.7871.47 or later. For enterprise environments, ensure mobile device management policies enforce the Chrome update.

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

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google Chrome is installed on iOS
    Locate the Chrome app icon on the iOS device home screen or in the app library. Chrome has a multi-colored circle icon with a blue 'C' in the center.
    Affected if Chrome is not installed on the iOS device, the system is not affected by this CVE.
  2. Identify the installed Chrome version on iOS
    Open Chrome, tap the three-dot menu in the top-right, select 'Settings', then tap 'Chrome' at the top. The version number is displayed under the Chrome name. Alternatively, navigate to chrome://version in the address bar.
    Affected if Unable to determine the version, assume the worst-case scenario and treat as potentially affected.
  3. Compare version against affected range
    Take the installed version number (e.g., 150.0.7871.x) and compare it numerically to 150.0.7871.47. Any version lower than 150.0.7871.47 falls within the affected range.
    Affected if The installed version is less than 150.0.7871.47 (for example, 150.0.7871.40 or 149.x.x.x).
  4. Verify WebAuthentication API is accessible
    The WebAuthentication API is built into Chrome and automatically available. No configuration toggle is needed. The vulnerability triggers when a user visits a crafted HTML page that attempts to use the WebAuthentication API.
    Affected if The WebAuthentication API is disabled or blocked via enterprise policy, reducing the attack surface but not eliminating the risk entirely.

The environment is affected if Google Chrome on iOS is installed with a version lower than 150.0.7871.47 and the WebAuthentication API is accessible to web pages, allowing a remote attacker to leak cross-origin data via a side-channel attack.

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

Update Google Chrome on iOS to version 150.0.7871.47 or later. For enterprise environments, ensure mobile device management policies enforce the Chrome update.

Recommended fix High confidence

Chrome iOS 150.0.7871.47 or later

  1. Open the App Store on your iOS device
  2. Search for Google Chrome or go to your installed apps
  3. Tap Update next to Chrome if an update is available, or enable automatic updates for all apps
  4. Alternatively, delete Chrome and reinstall from the App Store to ensure you have the latest version
  5. After updating, verify the version by going to Chrome > Settings > About Chrome (the version should be 150.0.7871.47 or higher)

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