Inappropriate implementation in CORS in Google Chrome prior to 151.0.7922.169 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
CVE-2026-76033
Score 4.2 from GitHub Security Advisory published 2026-08-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.2; 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.2
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 4.2(high)
- 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 computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0826575033.htmlVendor Advisories for CVE-2026-76033(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 16× in last 7d / 16× 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-20 22:56 UTCEPSS rescore
- 2026-08-20 19:38 UTCGHSA enrichment
- 2026-08-20 14:19 UTCEG score recompute
- 2026-08-20 14:19 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:04 UTCEG score recompute
- 2026-08-19 13:04 UTCGHSA enrichment
- 2026-08-19 12:25 UTCGHSA enrichment
- 2026-08-19 11:38 UTCEG score recompute▼ 4.60
- 2026-08-19 11:38 UTCGHSA enrichment
- 2026-08-19 11:37 UTCMITRE cvelistV5CVSS v3 → 4.2 · severity → MEDIUM
- 2026-08-19 08:42 UTCGHSA enrichment
- 2026-08-18 21:36 UTCGHSA enrichment
- 2026-08-18 21:22 UTCNVD update
- 2026-08-18 20:43 UTCEG score recompute
- 2026-08-18 20:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-76033?
When was CVE-2026-76033 disclosed?
Is CVE-2026-76033 actively exploited?
What is the CVSS score of CVE-2026-76033?
How do I remediate CVE-2026-76033?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76033
Is Your Infrastructure Affected by CVE-2026-76033?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.