CVE-2016-1640

The Web Store inline-installer implementation in the Extensions UI in Google Chrome before 49.0.2623.75 does not block installations upon deletion of an installation frame, which makes it easier for remote attackers to trick a user into believing that an installation request originated from the user's next navigation target via a crafted web site.

Published: 2016-03-06 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-1640 is rated Low Risk (39.4/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 1.15%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-1640

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.84% 1.15% +0.31%
2 2025-07-10 0.72% 0.84% +0.12%
3 2025-03-19 — 0.72% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [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-1640

OS Trackers for CVE-2016-1640

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

Affected software / configurations for CVE-2016-1640

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

References for CVE-2016-1640

cvelogic Threat Intelligence