Privilege elevation in Import in Google Chrome prior to 151.0.7922.173 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted file. (Chromium security severity: High)
CVE-2026-76018
Google's Chromium security team rated this High in the advisory text — the exact wording is "(Chromium security severity: High)". 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 8.8 (HIGH), derived from the VENDOR'S OWN SEVERITY BAND — not from a CVSS vector. That number is calibrated, not assumed: across 1101 Chromium CVEs that NVD has since scored, a Chromium "High" carried a median CVSS v3 base of 8.8. This score is provisional and will be superseded the moment any source publishes a real CVSS base. Confidence: LOW.
- 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
- —
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 20, 2026
Last Modified
August 20, 2026
References (2)
- chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0404570826.html
- chrome-cve-admin@googlehttps://issues.chromium.org/issues/513757918
Vendor Advisories for CVE-2026-76018(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-20 21:21 UTCNVD update
- 2026-08-20 20:57 UTCEG score recompute
- 2026-08-20 20:56 UTCMITRE cvelistV5first tracked
Frequently asked(3)
What is CVE-2026-76018?
When was CVE-2026-76018 disclosed?
How do I remediate CVE-2026-76018?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76018
Is Your Infrastructure Affected by CVE-2026-76018?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.