Insufficient data validation in Extensions API in Google Chrome prior to 68.0.3440.75 allowed an attacker who convinced a user to install a…

published 2019-06-27 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-7921

cvss: 6.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits: 0; none known

Insufficient data validation in Extensions API in Google Chrome prior to 68.0.3440.75 allowed an attacker who convinced a user to install a malicious extension to bypass navigation restrictions via a crafted Chrome Extension.

Patch / fix

fixed in 1 distros 1

Google Chrome 68.0.3440.75

chromium-browser RHEL 6 EXTRAS 68.0.3440.75-1.el6_10

red hat advisories RHSA-2018:2282

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-16064 updated 2026-06-28 cvss 4.3

chromium-browser: Request privilege escalation in Extensions

Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 68.0.3440.75-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 68.0.3440.75-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 68.0.3440.75-1.el6_10
fixed: vendor fix RHSA-2018:2282

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.0	6.5	CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

Google Chrome

Classification

Weakness

CWE-20 Improper Input Validation

Technology feeds

Google Chrome rss critical rss

References

Sources

CVE List CVE-2018-16064
NVD CVE-2018-16064

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary