CVE-2018-16072

MEDIUMNVD 6.56.5—Trending — 3 sources updated this week

6.5

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.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 34.7%
KEV: Not listed

Published

January 9, 2019

Last Modified

November 21, 2024

References (8)

chrome-cve-admin@googlehttp://www.securityfocus.com/bid/105215
chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html
chrome-cve-admin@googlehttps://crbug.com/864283
chrome-cve-admin@googlehttps://security.gentoo.org/glsa/201811-10
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/105215
af854a3a-2127-422b-91ae-364da2661108https://chromereleases.googleblog.com/2018/09/stable-channel-update-for-desktop.html
af854a3a-2127-422b-91ae-364da2661108https://crbug.com/864283
af854a3a-2127-422b-91ae-364da2661108https://security.gentoo.org/glsa/201811-10

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-346Origin Validation Error

Data Freshness Timeline

(refreshed 12× in last 7d / 19× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 23:38 UTCEG score recompute
2026-05-27 23:38 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 16:16 UTCOSV refresh

Frequently asked(5)

What is CVE-2018-16072?

CVE-2018-16072 is a medium vulnerability published on January 9, 2019. 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.

When was CVE-2018-16072 disclosed?

CVE-2018-16072 was first published in the National Vulnerability Database on January 9, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-16072 actively exploited?

CVE-2018-16072 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-16072?

CVE-2018-16072 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2018-16072?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-16072, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-16072

Explore →

Is Your Infrastructure Affected by CVE-2018-16072?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2018-16072

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-16072?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)