Skip to content
Fencer Vulns
medium 6.5

CVE-2026-13879 json

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…

published 2026-06-30 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-40565

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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)

Patch / fix

  • google chrome 150.0.7871.46
  • chromium Debian 12 150.0.7871.46-1~deb12u1
  • chromium Debian 13 150.0.7871.46-1~deb13u1
  • chromium Debian 14 150.0.7871.46-1

debian advisories DEBIAN-CVE-2026-13879

  • chromium openSUSE Leap 16.0 150.0.7871.186-bp160.1.1
  • chromium openSUSE Tumbleweed 150.0.7871.46-1.1

opensuse advisories openSUSE-SU-2026:21498-1openSUSE-SU-2026:11184-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-13879 updated cvss 5.7

chromium-browser: Use after free in Bluetooth

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 6.5 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.