CVE-2018-6333

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 2.3%, top 18% of all CVEs by exploit prediction. 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
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The hhvm-attach deep link handler in Nuclide did not properly sanitize the provided hostname parameter when rendering. As a result, a malicious URL could be used to render HTML and other content inside of the editor's context, which could potentially be chained to lead to code execution. This issue affected Nuclide prior to v0.290.0.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

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
Severity98% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
82%
KEV
Not listed

Published

December 31, 2018

Last Modified

May 6, 2025

Advisory Details (1)

Auto-updated May 25, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit 65f6bbd68340 (facebook/nuclide)

Patch available: facebook/nuclide v0.299.0 (contains commit 65f6bbd68340)

https://github.com/facebook/nuclide/commit/65f6bbd683404be1bb569b8d1be84b5d4c74a324

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
nuclide—0.290.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 44× 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.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-6333?
CVE-2018-6333 is a critical vulnerability published on December 31, 2018. The hhvm-attach deep link handler in Nuclide did not properly sanitize the provided hostname parameter when rendering. As a result, a malicious URL could be used to render HTML and other content inside of the editor's context, which could potentially be chained to lead to code execution. This issue…
When was CVE-2018-6333 disclosed?
CVE-2018-6333 was first published in the National Vulnerability Database on December 31, 2018, with the most recent update on May 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-6333 actively exploited?
CVE-2018-6333 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 18.2% of all scored CVEs.
What is the CVSS score of CVE-2018-6333?
CVE-2018-6333 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2018-6333?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6333, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-6333

Explore →

Is Your Infrastructure Affected by CVE-2018-6333?

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

Start Free Scan →Browse All CVEs