CVE-2018-16072 json
A missing origin check related to HLS manifests in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypass same or…
published 2019-01-09 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-7929
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 56%
- public exploits
- 0
- none known
Summary
A missing origin check related to HLS manifests in Blink in Google Chrome prior to 69.0.3497.81 allowed a remote attacker to bypass same origin policy via a crafted HTML page.
Patch / fix
- Google Chrome 69.0.3497.81
- chromium-browser Ubuntu 16.04 LTS 69.0.3497.81-0ubuntu0.16.04.1
- chromium-browser Ubuntu 18.04 LTS 69.0.3497.81-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2018-16072
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
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-16072 updated cvss 6.5
chromium-browser: Cross origin pixel leak in Chrome's interaction with Android's MediaPlayer
-
Red Hat Enterprise Linux 6 chromium-browsernot affected: vulnerable code not present
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.78% chance of exploitation in the next 30 days, higher than 56% 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:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-346 Origin Validation Error
- Technology feeds
References
Sources
- CVE List CVE-2018-16072
- NVD CVE-2018-16072
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.