Improper control of a resource through its lifetime in Workers 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: Low)
CVE-2026-79289
Google's Chromium security team rated this Low in the advisory text — the exact wording is "(Chromium security severity: Low)". Chromium's CNA does not publish a CVSS vector, and NVD has not yet analysed this record, so there is no CVSS v3.1, v4.0 or v2.0 base score for it from any source. EchelonGraph publishes 5.4 (MEDIUM), derived from the VENDOR'S OWN SEVERITY BAND — not from a CVSS vector. That number is calibrated, not assumed: across 413 Chromium CVEs that NVD has since scored, a Chromium "Low" carried a median CVSS v3 base of 5.4. Note that Chromium's "Low" is not CVSS LOW: only 9 of 413 such CVEs were scored below 4.0 by NVD, and 71% landed in CVSS MEDIUM. Chromium's bands express Google's triage priority, not CVSS severity. This score is provisional and will be superseded the moment any source publishes a real CVSS base. Confidence: LOW.
- 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
- —
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 5.4(low)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 25, 2026
References (2)
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html
- chrome-cve-admin@googlehttps://issues.chromium.org/issues/497876969
Vendor Advisories for CVE-2026-79289(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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-08-25 21:26 UTCNVD update
- 2026-08-25 20:27 UTCEG score recompute
- 2026-08-25 20:25 UTCMITRE cvelistV5first tracked
Frequently asked(3)
What is CVE-2026-79289?
When was CVE-2026-79289 disclosed?
How do I remediate CVE-2026-79289?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79289
Is Your Infrastructure Affected by CVE-2026-79289?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.