CVE-2015-8851

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 2.3% (82nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

node-uuid before 1.4.4 uses insufficiently random data to create a GUID, which could make it easier for attackers to have unspecified impact via brute force guessing.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
35
EG Risk 35/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation2% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
2.3%
EPSS %ILE
82nd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 30, 2020

Last Modified

October 7, 2026

Advisory Details (3)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, redhat.
redhatMentions a patch (unverified)

1327056 – (CVE-2015-8851) CVE-2015-8851 nodejs-node-uuid: insecure entropy source - Math.random()

https://bugzilla.redhat.com/show_bug.cgi?id=1327056
generic

oss-security - Re: CVE for nodejs node-uuid

http://www.openwall.com/lists/oss-security/2016/04/13/8
github_commit

commit 672f3834ed02 (broofa/node-uuid)

Fix landed in broofa/node-uuid commit 672f3834ed02 — awaiting tagged release

https://github.com/broofa/node-uuid/commit/672f3834ed02c798aa021c618d0a5666c8da000d

Vendor Advisories for CVE-2015-8851(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatheapster-0:1.1.0-1.beta2.el72016-06-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-uuid—
  • every version up to 1.4.7-1: fixed in 1.4.7-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-uuid—
  • every version up to 1.4.7-1: fixed in 1.4.7-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-uuid—
  • every version up to 1.4.7-1: fixed in 1.4.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-uuid—
  • every version up to 1.4.7-1: fixed in 1.4.7-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
node-uuid—
  • every version up to 1.4.4: fixed in 1.4.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-10-10 19:54 UTCEPSS rescore
  2. 2026-10-09 20:01 UTCEPSS rescore
  3. 2026-10-08 16:35 UTCEPSS rescore
  4. 2026-10-07 23:40 UTCEPSS rescore
  5. 2026-10-07 21:47 UTCVendor advisory
  6. 2026-10-07 20:46 UTCEG score recompute
  7. 2026-10-07 20:46 UTCVendor advisory
  8. 2026-10-06 15:11 UTCEPSS rescore
  9. 2026-10-05 17:38 UTCEPSS rescore
  10. 2026-10-04 23:17 UTCEPSS rescore
  11. 2026-10-03 14:21 UTCEPSS rescore
  12. 2026-09-30 14:58 UTCEPSS rescore
  13. 2026-09-30 14:58 UTCEPSS rescore
  14. 2026-09-30 09:08 UTCEG score recompute
  15. 2026-09-28 13:45 UTCEPSS rescore
  16. 2026-09-27 13:40 UTCEPSS rescore
  17. 2026-09-27 10:37 UTCOSV refresh
  18. 2026-09-26 15:53 UTCEPSS rescore
  19. 2026-09-26 15:53 UTCEPSS rescore
  20. 2026-09-23 13:41 UTCEPSS rescore
  21. 2026-09-20 20:09 UTCEPSS rescore
  22. 2026-09-19 15:35 UTCEPSS rescore
  23. 2026-09-18 19:22 UTCEPSS rescore
  24. 2026-09-17 19:21 UTCEPSS rescore
  25. 2026-09-15 03:05 UTCEPSS rescore
Show 75 more
  1. 2026-09-13 16:41 UTCEPSS rescore
  2. 2026-09-12 14:55 UTCEPSS rescore
  3. 2026-09-11 09:31 UTCEPSS rescore
  4. 2026-09-10 09:26 UTCEPSS rescore
  5. 2026-09-07 19:51 UTCOSV refresh
  6. 2026-09-06 13:42 UTCEPSS rescore
  7. 2026-09-04 13:55 UTCEPSS rescore
  8. 2026-09-02 14:07 UTCEPSS rescore
  9. 2026-09-01 13:48 UTCEPSS rescore
  10. 2026-09-01 03:31 UTCEPSS rescore
  11. 2026-08-27 14:20 UTCEPSS rescore
  12. 2026-08-26 14:41 UTCEPSS rescore
  13. 2026-08-25 13:44 UTCEPSS rescore
  14. 2026-08-23 00:13 UTCEPSS rescore
  15. 2026-08-21 23:44 UTCEPSS rescore
  16. 2026-08-21 05:44 UTCOSV refresh
  17. 2026-08-20 22:50 UTCEPSS rescore
  18. 2026-08-19 16:59 UTCEPSS rescore
  19. 2026-08-18 13:43 UTCEPSS rescore
  20. 2026-08-16 14:51 UTCEPSS rescore
  21. 2026-08-16 02:09 UTCEPSS rescore
  22. 2026-08-15 01:25 UTCEPSS rescore
  23. 2026-08-12 13:46 UTCEPSS rescore
  24. 2026-08-11 13:36 UTCEPSS rescore
  25. 2026-08-09 13:42 UTCEPSS rescore
  26. 2026-08-08 16:32 UTCEPSS rescore
  27. 2026-08-07 16:22 UTCEPSS rescore
  28. 2026-08-06 13:42 UTCEPSS rescore
  29. 2026-08-05 20:24 UTCOSV refresh
  30. 2026-08-05 19:12 UTCEPSS rescore
  31. 2026-08-04 15:04 UTCEPSS rescore
  32. 2026-08-04 10:31 UTCEPSS rescore
  33. 2026-08-01 04:11 UTCEPSS rescore
  34. 2026-07-30 01:26 UTCEPSS rescore
  35. 2026-07-30 01:26 UTCEPSS rescore
  36. 2026-07-28 15:31 UTCEPSS rescore
  37. 2026-07-26 14:50 UTCEPSS rescore
  38. 2026-07-25 14:13 UTCEPSS rescore
  39. 2026-07-24 14:13 UTCEPSS rescore
  40. 2026-07-23 14:14 UTCEPSS rescore
  41. 2026-07-23 01:20 UTCEG score recompute
  42. 2026-07-23 00:21 UTCEG score recompute
  43. 2026-07-22 22:00 UTCEG score recompute
  44. 2026-07-22 14:04 UTCEPSS rescore
  45. 2026-07-21 15:21 UTCEPSS rescore
  46. 2026-07-21 15:21 UTCEPSS rescore
  47. 2026-07-20 17:03 UTCEPSS rescore
  48. 2026-07-19 20:48 UTCOSV refresh
  49. 2026-07-19 14:27 UTCEPSS rescore
  50. 2026-07-19 14:27 UTCEPSS rescore
  51. 2026-07-19 02:26 UTCEPSS rescore
  52. 2026-07-19 02:26 UTCEPSS rescore
  53. 2026-07-18 10:00 UTCEPSS rescore
  54. 2026-07-16 16:59 UTCEPSS rescore
  55. 2026-07-15 16:54 UTCEPSS rescore
  56. 2026-07-15 16:54 UTCEPSS rescore
  57. 2026-07-15 01:56 UTCEPSS rescore
  58. 2026-07-13 22:26 UTCEPSS rescore
  59. 2026-07-13 22:26 UTCEPSS rescore
  60. 2026-07-12 05:42 UTCEPSS rescore
  61. 2026-07-11 08:23 UTCEPSS rescore
  62. 2026-07-09 19:05 UTCEPSS rescore
  63. 2026-07-09 19:05 UTCEPSS rescore
  64. 2026-07-08 15:10 UTCEPSS rescore
  65. 2026-07-07 13:42 UTCEPSS rescore
  66. 2026-07-07 13:42 UTCEPSS rescore
  67. 2026-07-06 16:24 UTCEPSS rescore
  68. 2026-07-06 02:20 UTCEPSS rescore
  69. 2026-07-05 02:26 UTCEPSS rescore
  70. 2026-07-04 06:28 UTCEPSS rescore
  71. 2026-07-02 11:11 UTCOSV refresh
  72. 2026-07-01 15:02 UTCEPSS rescore
  73. 2026-06-30 23:19 UTCEPSS rescore
  74. 2026-06-30 23:19 UTCEPSS rescore
  75. 2026-06-28 14:04 UTCEPSS rescore

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:node-uuid

Frequently asked(5)

What is CVE-2015-8851?
CVE-2015-8851 is a high vulnerability published on January 30, 2020. node-uuid before 1.4.4 uses insufficiently random data to create a GUID, which could make it easier for attackers to have unspecified impact via brute force guessing.
When was CVE-2015-8851 disclosed?
CVE-2015-8851 was first published on January 30, 2020, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-8851 actively exploited?
CVE-2015-8851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.3% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2015-8851?
CVE-2015-8851 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2015-8851?
A fix for CVE-2015-8851 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2015-8851 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2015-8851

Explore →

Is Your Infrastructure Affected by CVE-2015-8851?

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

Book a Demo →Browse All CVEs