Inappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
CVE-2026-11167
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 9.6(medium)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.htmlVendor Advisories for CVE-2026-11167(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 148.0.7778.96-3 (363 versions) | 149.0.7827.53-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions) | 149.0.7827.53-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (130 versions) | 149.0.7827.53-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 33× in last 7d / 258× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 613 total refreshes for this CVE.
- 2026-08-25 06:18 UTCGHSA enrichment
- 2026-08-25 02:17 UTCEG score recompute
- 2026-08-25 02:17 UTCGHSA enrichment
- 2026-08-23 23:50 UTCVendor advisory
- 2026-08-23 23:50 UTCGHSA enrichment
- 2026-08-23 20:09 UTCVendor advisory
- 2026-08-23 20:09 UTCGHSA enrichment
- 2026-08-23 16:21 UTCVendor advisory
- 2026-08-23 16:21 UTCGHSA enrichment
- 2026-08-23 12:32 UTCEG score recompute
- 2026-08-23 12:32 UTCVendor advisory
- 2026-08-23 12:32 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 23:48 UTCVendor advisory
- 2026-08-21 23:48 UTCGHSA enrichment
- 2026-08-21 20:07 UTCGHSA enrichment
- 2026-08-21 12:54 UTCVendor advisory
- 2026-08-21 12:54 UTCGHSA enrichment
- 2026-08-21 06:45 UTCVendor advisory
- 2026-08-21 06:45 UTCGHSA enrichment
- 2026-08-21 00:57 UTCEG score recompute
- 2026-08-21 00:57 UTCVendor advisory
- 2026-08-21 00:56 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-20 21:16 UTCVendor advisory
- 2026-08-20 21:16 UTCGHSA enrichment
- 2026-08-20 17:27 UTCVendor advisory
- 2026-08-20 17:27 UTCGHSA enrichment
- 2026-08-20 09:48 UTCEG score recompute
- 2026-08-20 09:48 UTCVendor advisory
- 2026-08-20 09:48 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:03 UTCEG score recompute
- 2026-08-17 14:03 UTCVendor advisory
- 2026-08-17 14:03 UTCGHSA enrichment
- 2026-08-17 10:22 UTCVendor advisory
- 2026-08-17 10:22 UTCGHSA enrichment
- 2026-08-17 06:41 UTCVendor advisory
- 2026-08-17 06:41 UTCGHSA enrichment
- 2026-08-17 02:33 UTCVendor advisory
- 2026-08-17 02:33 UTCGHSA enrichment
- 2026-08-16 16:54 UTCEG score recompute
- 2026-08-16 16:54 UTCVendor advisory
- 2026-08-16 16:54 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:14 UTCVendor advisory
- 2026-08-16 13:14 UTCGHSA enrichment
- 2026-08-16 09:30 UTCVendor advisory
- 2026-08-16 09:30 UTCGHSA enrichment
- 2026-08-16 05:50 UTCEG score recompute
- 2026-08-16 05:50 UTCVendor advisory
- 2026-08-16 05:50 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:09 UTCVendor advisory
- 2026-08-16 02:09 UTCGHSA enrichment
- 2026-08-15 18:23 UTCVendor advisory
- 2026-08-15 18:23 UTCGHSA enrichment
- 2026-08-15 13:21 UTCVendor advisory
- 2026-08-15 13:21 UTCGHSA enrichment
- 2026-08-15 04:02 UTCEG score recompute
- 2026-08-15 04:02 UTCVendor advisory
- 2026-08-15 04:02 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:18 UTCVendor advisory
- 2026-08-15 00:18 UTCGHSA enrichment
- 2026-08-14 20:38 UTCVendor advisory
- 2026-08-14 20:38 UTCGHSA enrichment
- 2026-08-14 16:57 UTCVendor advisory
- 2026-08-14 16:57 UTCGHSA enrichment
- 2026-08-14 13:15 UTCVendor advisory
- 2026-08-14 13:15 UTCGHSA enrichment
- 2026-08-14 09:35 UTCVendor advisory
- 2026-08-14 09:35 UTCGHSA enrichment
- 2026-08-14 05:54 UTCVendor advisory
- 2026-08-14 05:54 UTCGHSA enrichment
- 2026-08-14 02:14 UTCVendor advisory
- 2026-08-14 02:14 UTCGHSA enrichment
- 2026-08-13 22:33 UTCEG score recompute
- 2026-08-13 22:33 UTCVendor advisory
- 2026-08-13 22:33 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 15:11 UTCVendor advisory
- 2026-08-13 15:11 UTCGHSA enrichment
- 2026-08-13 10:07 UTCVendor advisory
- 2026-08-13 10:06 UTCGHSA enrichment
- 2026-08-13 06:26 UTCVendor advisory
- 2026-08-13 06:26 UTCGHSA enrichment
- 2026-08-13 02:46 UTCGHSA enrichment
- 2026-08-12 23:05 UTCGHSA enrichment
- 2026-08-12 19:24 UTCVendor advisory
- 2026-08-12 19:24 UTCGHSA enrichment
- 2026-08-12 15:44 UTCEG score recompute
- 2026-08-12 15:44 UTCVendor advisory
- 2026-08-12 15:44 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 11:58 UTCVendor advisory
- 2026-08-12 11:58 UTCGHSA enrichment
- 2026-08-12 08:17 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-11167?
When was CVE-2026-11167 disclosed?
Is CVE-2026-11167 actively exploited?
What is the CVSS score of CVE-2026-11167?
How do I remediate CVE-2026-11167?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11167
Is Your Infrastructure Affected by CVE-2026-11167?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.