Skip to content
major vulnerability· requires attention

Widely used Chrome browser; enterprise endpoints at risk via user-installed malicious extensions; high-severity escalation.

Web

CVE-2026-11092

8.8
High
EPSS 0.18%Patch availableJun 6, 2026

Privilege escalation via malicious Chrome extension (DevTools policy gap).

common questions

Is CVE-2026-11092 being exploited?

Not confirmed. CVE-2026-11092 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-11092?

CVE-2026-11092 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-11092?

Yes. A fix has been recorded for CVE-2026-11092. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-11092 affect?

CVE-2026-11092 affects Google Chrome <=149.0.7827.53, Chrome DevTools extension policy. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-11092?

Update to Chrome 149.0.7827.53 or newer

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome <=149.0.7827.53Chrome DevTools extension policy
impact

Attacker can escalate within Chrome by tricking a user into installing a crafted extension; may access browser data and permissions.

action required

Patch when possible

affected versions
Google Chrome
  • affected< 149.0.7827.53

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free