Insufficient policy enforcement in Navigation in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
CVE-2026-15130
Score 4.3 from GitHub Security Advisory published 2026-07-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 4.3(medium)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 9, 2026
Advisory Details (2)
Auto-updated Jul 9, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01162222768.htmlVendor Advisories for CVE-2026-15130(1)
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 ... 150.0.7871.46-1~deb13u1 (384 versions) | 150.0.7871.114-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (150 versions) | 150.0.7871.114-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (151 versions) | 150.0.7871.114-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 24× in last 7d / 106× 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 138 total refreshes for this CVE.
- 2026-08-26 04:42 UTCEG score recompute
- 2026-08-26 04:42 UTCVendor advisory
- 2026-08-26 04:42 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 04:03 UTCEG score recompute
- 2026-08-25 04:03 UTCVendor advisory
- 2026-08-25 04:03 UTCGHSA enrichment
- 2026-08-24 03:59 UTCVendor advisory
- 2026-08-24 03:59 UTCGHSA enrichment
- 2026-08-23 03:46 UTCEG score recompute
- 2026-08-23 03:46 UTCVendor advisory
- 2026-08-23 03:46 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 03:43 UTCEG score recompute
- 2026-08-22 03:43 UTCVendor advisory
- 2026-08-22 03:43 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 02:04 UTCEG score recompute
- 2026-08-21 02:04 UTCVendor advisory
- 2026-08-21 02:04 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 01:54 UTCEG score recompute
- 2026-08-20 01:54 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 22:27 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-18 22:27 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:19 UTCEG score recompute
- 2026-08-17 22:19 UTCVendor advisory
- 2026-08-17 22:19 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 17:59 UTCEG score recompute
- 2026-08-16 17:59 UTCVendor advisory
- 2026-08-16 17:59 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:29 UTCEG score recompute
- 2026-08-15 17:29 UTCVendor advisory
- 2026-08-15 17:29 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:26 UTCEG score recompute
- 2026-08-14 17:26 UTCVendor advisory
- 2026-08-14 17:26 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 17:08 UTCVendor advisory
- 2026-08-13 17:08 UTCGHSA enrichment
- 2026-08-12 16:23 UTCEG score recompute
- 2026-08-12 16:23 UTCVendor advisory
- 2026-08-12 16:23 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 16:21 UTCEG score recompute
- 2026-08-11 16:21 UTCVendor advisory
- 2026-08-11 16:21 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 16:18 UTCGHSA enrichment
- 2026-08-09 16:01 UTCEG score recompute
- 2026-08-09 16:01 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 15:59 UTCEG score recompute
- 2026-08-08 15:59 UTCVendor advisory
- 2026-08-08 15:59 UTCGHSA enrichment
- 2026-08-07 15:56 UTCVendor advisory
- 2026-08-07 15:56 UTCGHSA enrichment
- 2026-08-06 15:54 UTCEG score recompute
- 2026-08-06 15:54 UTCVendor advisory
- 2026-08-06 15:54 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:51 UTCEG score recompute
- 2026-08-05 15:51 UTCVendor advisory
- 2026-08-05 15:51 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 13:41 UTCEG score recompute
- 2026-08-04 13:41 UTCVendor advisory
- 2026-08-04 13:40 UTCGHSA enrichment
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 12:56 UTCEG score recompute
- 2026-08-03 12:56 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 12:50 UTCEG score recompute
- 2026-08-02 12:50 UTCVendor advisory
- 2026-08-02 12:50 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 12:47 UTCEG score recompute
- 2026-08-01 12:47 UTCVendor advisory
- 2026-08-01 12:47 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 12:41 UTCEG score recompute
- 2026-07-31 12:41 UTCVendor advisory
- 2026-07-31 12:41 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 12:38 UTCEG score recompute
- 2026-07-30 12:38 UTCVendor advisory
- 2026-07-30 12:37 UTCGHSA enrichment
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 12:31 UTCEG score recompute
- 2026-07-29 12:31 UTCVendor advisory
- 2026-07-29 12:31 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-15130?
When was CVE-2026-15130 disclosed?
Is CVE-2026-15130 actively exploited?
What is the CVSS score of CVE-2026-15130?
How do I remediate CVE-2026-15130?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15130
Is Your Infrastructure Affected by CVE-2026-15130?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.