Incomplete cleanup in SiteIsolation in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)
CVE-2026-78903
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.1; 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
- 3.1
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 3.1(high)
- EG Risk
- 30(Track)EG Risk 30/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 computedSeverity31% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
September 17, 2026
References (2)
Vendor Advisories for CVE-2026-78903(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 152.0.7977.64-1 (412 versions) | 152.0.7977.75-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 152.0.7977.75-1~deb12u1 (178 versions) | 152.0.7977.75-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 152.0.7977.75-1~deb13u1 (180 versions) | — | — |
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 14× in last 7d / 52× 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.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:04 UTCEG score recompute
- 2026-09-17 19:04 UTCVendor advisory
- 2026-09-17 19:03 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 14:11 UTCEG score recompute
- 2026-09-15 14:11 UTCVendor advisory
- 2026-09-15 14:11 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-12 14:52 UTCEG score recompute
- 2026-09-12 14:52 UTCVendor advisory
- 2026-09-12 14:52 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-09 15:33 UTCEG score recompute
- 2026-09-09 15:33 UTCVendor advisory
- 2026-09-09 15:33 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-06 16:13 UTCEG score recompute
- 2026-09-06 16:13 UTCVendor advisory
- 2026-09-06 16:13 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
Show 27 moreShow fewer
- 2026-09-03 16:54 UTCEG score recompute
- 2026-09-03 16:54 UTCVendor advisory
- 2026-09-03 16:54 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 17:34 UTCEG score recompute
- 2026-08-31 17:34 UTCVendor advisory
- 2026-08-31 17:34 UTCGHSA enrichment
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:14 UTCEG score recompute
- 2026-08-28 16:13 UTCGHSA enrichment
- 2026-08-27 20:19 UTCEG score recompute▼ 3.40
- 2026-08-27 20:19 UTCGHSA enrichment
- 2026-08-27 20:13 UTCMITRE cvelistV5CVSS v3 → 3.1 · severity → LOW
- 2026-08-27 16:31 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 16:40 UTCEG score recompute
- 2026-08-26 16:40 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 21:25 UTCNVD update
- 2026-08-25 20:29 UTCEG score recompute
- 2026-08-25 20:25 UTCMITRE cvelistV5first tracked
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCvxssroott/CVE-2026-78903-SWIFT-Kick-to-the-CredsFirst seen Aug 30, 2026
Offensive Research & Exploit Development. Vulnerability research, PoC development, and offensive tooling for financial infrastructure.
Open source ↗
Frequently asked(5)
What is CVE-2026-78903?
When was CVE-2026-78903 disclosed?
Is CVE-2026-78903 actively exploited?
What is the CVSS score of CVE-2026-78903?
How do I remediate CVE-2026-78903?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-78903
Is Your Infrastructure Affected by CVE-2026-78903?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.