CVE-2016-10578 json
Downloads Resources over HTTP in unicode
published 8y ago modified 4mo ago also GHSA-qjf4-7642-c57p , EUVD-2019-0330
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
unicode loads unicode data downloaded from unicode.org into nodejs. Unicode before 9.0.0 downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks.
Patch / fix
- npm unicode 9.0.0
- unicode_project unicode 9.0.0
Is CVE-2016-10578 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-10578 updated cvss 4.2
nodejs-unicode: Downloads resources over HTTP
-
Red Hat All currently supported Red Hat productsnot 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.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | unicode | <9.0.0 |
9.0.0 |
Affected products
- HackerOne unicode node module
Classification
References
-
nodesecurity.io
/advisories/161
third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2016-10578
advisory
-
github.com
/advisories/GHSA-qjf4-7642-c57p
advisory
-
npmjs.com
/advisories/161
web
Sources
- CVE List CVE-2016-10578
- GitHub Advisory GHSA-qjf4-7642-c57p
- NVD CVE-2016-10578
Fencer Intel 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.