CVE-2016-1684

numbers.c in libxslt before 1.1.29, as used in Google Chrome before 51.0.2704.63, mishandles the i format token for xsl:number data, which allows remote attackers to cause a denial of service (integer overflow or resource consumption) or possibly have unspecified other impact via a crafted document.

Published: 2016-06-05 Last update: 2026-05-06 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2016-1684 is rated Moderate Risk (56.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.87%). Mandatory action: 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-1684

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-03-03 0.55% 0.87% +0.32%
2 2025-07-12 0.84% 0.55% -0.29%
3 2025-05-25 0.84%

Full EPSS history (16 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.6 5.9 [email protected]
5.1 2.0 MEDIUM
AV:N/AC:H/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
4.9 6.4 [email protected]

Weakness enumeration for CVE-2016-1684

OS Trackers for CVE-2016-1684

vendor priority summary link
debian not yet assigned CVE-2016-1684 not yet assigned priority: Debian including 1 source packages (libxslt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2016-1684
gentoo normal CVE-2016-1684: 1 GLSA(s) (201607-07), 1 atom(s) (www-client/chromium); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2016-1684
redhat medium https://access.redhat.com/security/cve/CVE-2016-1684
suse medium CVE-2016-1684 severity moderate: SUSE including 8 source package names (chromedriver-55.0.2883.75-3.1, chromium-101.0.4951.64-bp154.1.2, …), 8 product×package rows across 5 product lines (openSUSE Leap 15.0, openSUSE Leap 15.2, … (5 product lines)): Fixed 8. https://www.suse.com/security/cve/CVE-2016-1684/
ubuntu medium CVE-2016-1684 medium priority: Ubuntu including 3 source packages (chromium-browser, libxslt, oxide-qt), 21 status rows across 7 suites (precise, trusty, upstream, wily, xenial, yakkety, zesty): released 15, ignored 3, not-affected 2, DNE 1. https://ubuntu.com/security/CVE-2016-1684

NVD evaluator notes for CVE-2016-1684

Comment: <a href="http://cwe.mitre.org/data/definitions/190.html">CWE-190: Integer Overflow or Wraparound</a>

Affected software / configurations for CVE-2016-1684

Vendor Product Version Raw CPE
google chrome <= 50.0.2661.102 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
xmlsoft libxslt <= 1.1.28 cpe:2.3:a:xmlsoft:libxslt:*:*:*:*:*:*:*:*

References for CVE-2016-1684

URL Tags
http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html
http://lists.apple.com/archives/security-announce/2016/Jul/msg00000.html
http://lists.apple.com/archives/security-announce/2016/Jul/msg00001.html
http://lists.apple.com/archives/security-announce/2016/Jul/msg00002.html
http://lists.apple.com/archives/security-announce/2016/Jul/msg00003.html
http://lists.apple.com/archives/security-announce/2016/Jul/msg00005.html
http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.html
http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.html
http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.html
http://www.debian.org/security/2016/dsa-3590
http://www.debian.org/security/2016/dsa-3605
http://www.securityfocus.com/bid/90876
http://www.securitytracker.com/id/1035981
http://www.ubuntu.com/usn/USN-2992-1
https://access.redhat.com/errata/RHSA-2016:1190
https://bugzilla.redhat.com/show_bug.cgi?id=1340017
https://crbug.com/583171
https://git.gnome.org/browse/libxslt/commit/?id=91d0540ac9beaa86719a05b749219a69baa0dd8d
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/SK4YNISS22MJY22YX5I6V2U63QZAUEHA/
https://security.gentoo.org/glsa/201607-07
https://support.apple.com/HT206899
https://support.apple.com/HT206901
https://support.apple.com/HT206902
https://support.apple.com/HT206903
https://support.apple.com/HT206904
https://support.apple.com/HT206905
cvelogic Threat Intelligence