Skip to content
Fencer Intel
medium 5.3

CVE-2026-106214 json

Information leak in Proxy in Google Chrome on on Windows prior to 155.0.8059.39 allowed an adjacent attacker to obtain sensitive informatio…

published last mo. modified last mo. also EUVD-2026-93810

cvss
5.3
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 9%
public exploits
0
none known

Summary

Information leak in Proxy in Google Chrome on on Windows prior to 155.0.8059.39 allowed an adjacent attacker to obtain sensitive information via crafted network traffic. (Chromium security severity: High)

Patch / fix

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

debian advisories DEBIAN-CVE-2026-106214

  • chromium openSUSE Leap 16.0 155.0.8059.84-bp160.1.1
  • chromium openSUSE Tumbleweed 155.0.8059.39-1.1

opensuse advisories openSUSE-SU-2026:22124-1openSUSE-SU-2026:12091-1

Is CVE-2026-106214 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-106214 updated cvss 8.8

chromium-browser: Information leak in Proxy

  • 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
last mo.

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • issues.chromium.org https://issues.chromium.org/issues/533493992 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • Google Chrome

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Technology feeds

References

Sources

Fencer Intel 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.