dbcve.org
ChromeWeb browser · Google

CVE-2026-13887

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
Inappropriate implementation in NFC in Google Chrome on Android 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: 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

This is a cross-origin data leak vulnerability in the NFC (Near Field Communication) implementation of Google Chrome on Android. A remote attacker who has already compromised the renderer process can exploit inappropriate access controls in the NFC API to leak data from other origins via a crafted HTML page. The attack requires prior renderer compromise, making it a secondary exploitation scenario.

MitigationUpdate Google Chrome on Android to version 150.0.7871.47 or later to patch the NFC implementation. Organizations should ensure mobile devices are running current Chrome versions.

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. Identify the browser and platform
    Check if Google Chrome is running on an Android device. On the Android device, go to Settings > Apps > Chrome, or open chrome://version to see the browser details.
    Affected if The device is NOT running Google Chrome on Android - the vulnerability only affects Chrome on Android, not other browsers or platforms.
  2. Determine the installed Chrome version
    Open Chrome, tap the three-dot menu, go to Settings > About Chrome, or navigate to chrome://version. Note the version number shown (e.g., 150.0.7871.0).
    Affected if The installed version is less than 150.0.7871.47. Versions from 150.0.7871.47 onward include the security patch.
  3. Verify if NFC is enabled
    On the Android device, go to Settings > Connected devices > NFC (or Settings > Network & Internet > NFC on some versions). Check if NFC is turned on.
    Affected if NFC is enabled - the vulnerability exploits the NFC API, so NFC must be active for the data leak to occur through this attack vector.
  4. Assess renderer compromise risk
    Review the device for signs of compromise: unexpected apps, unusual battery drain, suspicious network connections, or if the device has been jailbroken/rooted without the user's knowledge.
    Affected if The renderer process has been compromised - this is a prerequisite for the attack. The vulnerability allows a compromised renderer to leak cross-origin data via NFC.

A user is affected if they are running Google Chrome on Android with version < 150.0.7871.47, NFC is enabled, and the renderer process has been compromised - all three conditions must be present for the cross-origin data leak to be exploitable.

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 Android to version 150.0.7871.47 or later to patch the NFC implementation. Organizations should ensure mobile devices are running current Chrome versions.

Recommended fix High confidence

Chrome 150.0.7871.47 or later for Android

  1. Open the Google Play Store app on your Android device
  2. Search for "Google Chrome" or "Chrome"
  3. Tap "Update" if an update is available, or verify the app is set to auto-update
  4. Alternatively, go to Chrome Settings > About Chrome and tap "Update Chrome"
  5. Verify the Chrome version is 150.0.7871.47 or later in chrome://version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.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-13887 — 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-13887 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