CVE-2016-5187

Google Chrome prior to 54.0.2840.85 for Android incorrectly handled rapid transition into and out of full screen mode, which allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via crafted HTML pages.

Published: 2016-12-18 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-5187 is rated Moderate Risk (49.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.22%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-5187

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.39% 1.22% +0.83%
2 2025-03-30 0.78% 0.39% -0.40%
3 2025-03-29 — 0.78% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-5187

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2016-5187

OS Trackers for CVE-2016-5187

vendor priority summary link
gentoo normal CVE-2016-5187: 1 GLSA(s) (201610-09), 1 atom(s) (www-client/chromium); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-5187
redhat high — https://access.redhat.com/security/cve/CVE-2016-5187
ubuntu medium CVE-2016-5187 medium priority: Ubuntu including 2 source packages (chromium-browser, oxide-qt), 10 status rows across 5 suites (precise, trusty, upstream, xenial, yakkety): released 4, not-affected 3, DNE 2, ignored 1. https://ubuntu.com/security/CVE-2016-5187

Affected software / configurations for CVE-2016-5187

Vendor Product Version Raw CPE
google chrome <= 53.0.2785.143 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2016-5187

cvelogic Threat Intelligence