ChromeWeb browser · Google

CVE-2026-13879

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30

Fix available

A fix is available. Upgrade to 150.0.7871.46 or later.

See remediation →

70/100

Remediation priority · Elevated

No privileges Zero-click 7 weeks old

Official description

NVD · unedited

Use after free in Bluetooth in Google Chrome prior to 150.0.7871.47 allowed an attacker on the local network segment to obtain potentially sensitive information from process memory via a malicious peripheral. (Chromium security severity: Medium)

Technical summary

dbcve analysis · high confidence

A use-after-free vulnerability exists in Google Chrome's Bluetooth implementation before version 150.0.7871.47. This memory safety flaw allows an attacker on the local network segment who can introduce a malicious peripheral to trigger the vulnerability and read potentially sensitive information from process memory after it has been deallocated.

MitigationUpdate Google Chrome to version 150.0.7871.47 or later to patch the use-after-free vulnerability in the Bluetooth component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 150.0.7871.46

CVSS breakdown

From the vector

Attack vector: Adjacent
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

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

Check installed Chrome version

Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' (Linux) or check 'C:\Program Files\Google\Chrome\Application\chrome.exe' version property (Windows)

Affected if Version is earlier than 150.0.7871.46 (e.g., 149.x.x.x or earlier)
Identify Chrome installation path and version on Windows

Open PowerShell and run: (Get-Item 'C:\Program Files\Google\Chrome\Application\chrome.exe').VersionInfo.FileVersion

Affected if Returns a version string lower than 150.0.7871.46
Identify Chrome installation path and version on Linux

Run 'google-chrome --version' or '/usr/bin/google-chrome --version' in terminal

Affected if Returns a version lower than 150.0.7871.46 (e.g., 149.0.6094.0 or earlier)
Check if Chrome Bluetooth API is accessible or in use

Examine Chrome's internal pages: navigate to chrome://bluetooth-internals/ in a Chrome tab (requires the browser to have Bluetooth support enabled)

Affected if The page loads successfully, indicating Bluetooth component is present and potentially active

A user is affected if their installed Google Chrome version is earlier than 150.0.7871.46 and the browser's Bluetooth feature is accessible or has been used on their system.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 150.0.7871.46 or later

Fixed in 150.0.7871.46

Interim mitigation

Update Google Chrome to version 150.0.7871.47 or later to patch the use-after-free vulnerability in the Bluetooth component.

Recommended fix High confidence

Chrome 150.0.7871.47 or later

Open Google Chrome and navigate to Settings > Help > About Google Chrome
Verify the current version number displayed
If the version is earlier than 150.0.7871.47, click 'Update Google Chrome' to download and install the latest version
Restart the browser after the update completes
Alternatively, download the latest Chrome installer from the official Google Chrome website and reinstall to ensure the newest 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

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

Primary sources

chromereleases.googleblog.comVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13879 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-13879?

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.

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

At a glance

A fix existsUpgrade to 150.0.7871.46 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-13879 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References