How severe is CVE-2026-106195?

No CVSS score has been assigned to CVE-2026-106195 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-106195?

Affected package information for CVE-2026-106195 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2026-106195?

No fixed release is recorded for CVE-2026-106195 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2026-106195 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2026-106195 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-106195 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-106195 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-106195?

CVE-2026-106195 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-106195?

CVE-2026-106195 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-106195 published, and has it been updated?

CVE-2026-106195 was published on October 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2026-106195 — Chrome

CVE-2026-106195 is a CWE-863 vulnerability. No vendor fix is recorded yet; mitigation options are listed below.

Incorrect authorization in Chromoting in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions via crafted network traffic. (Chromium…

Published

Oct 6, 2026

Updated

Oct 6, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs10th percentile — riskier than 10% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Incorrect authorization in Chromoting in Google Chrome on on Mac prior to 155.0.8059.39 allowed a remote attacker to bypass system access restrictions via crafted network traffic. (Chromium security severity: Low)

Affected Products

1 product · 1 configurations

Application

chromegoogle

< 155.0.8059.39

range

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2026-106195 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-106195 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works