Inappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.53 allowed an attacker in a privileged network position to execute arbitrary code inside a sandbox via a crafted Chrome Extension. (Chromium security severity: Low)
CVE-2026-11269
Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.1; 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
- 7.1
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
July 23, 2026
Advisory Details (2)
Auto-updated Jun 12, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.htmlVendor Advisories for CVE-2026-11269(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 21× in last 7d / 120× 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 299 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 02:13 UTCEG score recompute
- 2026-08-25 02:13 UTCGHSA enrichment
- 2026-08-23 23:50 UTCVendor advisory
- 2026-08-23 23:50 UTCGHSA enrichment
- 2026-08-23 12:29 UTCEG score recompute
- 2026-08-23 12:29 UTCVendor advisory
- 2026-08-23 12:29 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 20:07 UTCGHSA enrichment
- 2026-08-21 08:33 UTCEG score recompute
- 2026-08-21 08:33 UTCVendor advisory
- 2026-08-21 08:33 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:16 UTCVendor advisory
- 2026-08-20 21:16 UTCGHSA enrichment
- 2026-08-20 09:45 UTCEG score recompute
- 2026-08-20 09:45 UTCVendor advisory
- 2026-08-20 09:45 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-17 13:41 UTCGHSA enrichment
- 2026-08-17 02:25 UTCVendor advisory
- 2026-08-17 02:25 UTCGHSA enrichment
- 2026-08-16 14:48 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-16 14:48 UTCVendor advisory
- 2026-08-16 14:48 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:08 UTCVendor advisory
- 2026-08-16 02:08 UTCGHSA enrichment
- 2026-08-15 12:36 UTCEG score recompute
- 2026-08-15 12:36 UTCVendor advisory
- 2026-08-15 12:36 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:06 UTCVendor advisory
- 2026-08-14 21:06 UTCGHSA enrichment
- 2026-08-14 09:49 UTCGHSA enrichment
- 2026-08-13 22:32 UTCEG score recompute
- 2026-08-13 22:32 UTCVendor advisory
- 2026-08-13 22:32 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:01 UTCVendor advisory
- 2026-08-13 09:01 UTCGHSA enrichment
- 2026-08-12 21:44 UTCEG score recompute
- 2026-08-12 21:44 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 10:28 UTCVendor advisory
- 2026-08-12 10:28 UTCGHSA enrichment
- 2026-08-11 23:02 UTCEG score recompute
- 2026-08-11 23:02 UTCVendor advisory
- 2026-08-11 23:02 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 11:46 UTCVendor advisory
- 2026-08-11 11:46 UTCGHSA enrichment
- 2026-08-11 00:27 UTCEG score recompute
- 2026-08-11 00:27 UTCVendor advisory
- 2026-08-11 00:27 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 13:10 UTCGHSA enrichment
- 2026-08-10 01:53 UTCGHSA enrichment
- 2026-08-09 14:36 UTCEG score recompute
- 2026-08-09 14:36 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:20 UTCEG score recompute
- 2026-08-09 03:20 UTCVendor advisory
- 2026-08-09 03:20 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:03 UTCVendor advisory
- 2026-08-08 16:03 UTCGHSA enrichment
- 2026-08-08 04:46 UTCVendor advisory
- 2026-08-08 04:46 UTCGHSA enrichment
- 2026-08-07 17:29 UTCEG score recompute
- 2026-08-07 17:29 UTCVendor advisory
- 2026-08-07 17:29 UTCGHSA enrichment
- 2026-08-07 06:12 UTCVendor advisory
- 2026-08-07 06:12 UTCGHSA enrichment
- 2026-08-06 18:55 UTCEG score recompute
- 2026-08-06 18:55 UTCVendor advisory
- 2026-08-06 18:55 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 07:38 UTCVendor advisory
- 2026-08-06 07:38 UTCGHSA enrichment
- 2026-08-05 20:22 UTCEG score recompute
- 2026-08-05 20:22 UTCVendor advisory
- 2026-08-05 20:22 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 18:35 UTCEG score recompute
- 2026-08-04 18:35 UTCVendor advisory
- 2026-08-04 18:35 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 02:55 UTCVendor advisory
- 2026-08-04 02:55 UTCGHSA enrichment
- 2026-08-03 15:27 UTCVendor advisory
- 2026-08-03 15:27 UTCGHSA enrichment
- 2026-08-02 21:35 UTCVendor advisory
- 2026-08-02 21:35 UTCGHSA enrichment
- 2026-08-02 10:18 UTCVendor advisory
- 2026-08-02 10:18 UTCGHSA enrichment
- 2026-08-01 23:01 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-829
- CVE-2021-41037EG 10.0CRITICAL
- CVE-2022-1161EG 10.0EPSS p92CRITICAL
- CVE-2020-4561EG 10.0CRITICAL
- CVE-2022-24119EG 9.8CRITICAL
- CVE-2020-16152EG 9.8EPSS p98CRITICAL
- CVE-2021-21804EG 9.8CRITICAL
- CVE-2020-25414EG 9.8CRITICAL
- CVE-2020-3794EG 9.8EPSS p94CRITICAL
- CVE-2020-8128EG 9.8CRITICAL
- CVE-2012-4919EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-11269?
When was CVE-2026-11269 disclosed?
Is CVE-2026-11269 actively exploited?
What is the CVSS score of CVE-2026-11269?
How do I remediate CVE-2026-11269?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11269
Is Your Infrastructure Affected by CVE-2026-11269?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.