Vulnerability

CVE-2026-11170

High· 8.1CVSS8.1EPSS0%

.rules3/5

Inappropriate implementation in Chromoting in Google Chrome on Linux prior to 149.0.7827.53 allowed a remote attacker to perform OS-level privilege escalation via malicious network traffic. (Chromium security severity: Medium)

Threat signal

81/100

High

Severity

high

CVSS

8.1

EPSS

Active

CVSS

v3.1via NVDOpen in FIRST calculator →

8.1/ 10HIGHCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityHighRequires conditions outside attacker's control (race, brute-force, configuration
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

0.13%

probability of exploitation in next 30 days

p32

higher than 32% of all CVEs

3-day trend↑ 0pp

Low exploitation likelihood — defer if no other signals fire.

Vendor VEX

No VEX statements published for CVE-2026-11170. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCTrack

Total impact on non-trivial mission systems

exploitation: none
automatable: yes
impact: total
mission: support

Lifecycle

2026-06-04Published
2026-06-05Vendor advisory · microsoftCVE-2026-11170 — Chromium: CVE-2026-11170 Inappropriate implementation in Chromoting
2026-06-08Last modified1 source

Entity graph

2 nodes · 1 edges · click to pivot

CVEActorVendor advisoryIOCNews

Vendor advisories

microsoftCVE-2026-11170Chromium: CVE-2026-11170 Inappropriate implementation in Chromoting

References

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.