CVE-2018-21268

CRITICALNVD 10.09.8▼
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-24. NVD baseline CVSS 10.0; sources differ by 0.2.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 4%CVSS: 10.0Exploit: NoneExposed: 0

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

The traceroute (aka node-traceroute) package through 1.0.0 for Node.js allows remote command injection via the host parameter. This occurs because the Child.exec() method, which is considered to be not entirely safe, is used. In particular, an OS command can be placed after a newline character.

CVSS v3
10.0
EG Score
9.8(medium)
EPSS
90.0%
KEV
Not listed

Published

June 25, 2020

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Jul 11, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Tags · jaw187/node-traceroute · GitHub

https://github.com/jaw187/node-traceroute/tags
github_commit

commit b99ee024a01a (jaw187/node-traceroute)

Fix landed in jaw187/node-traceroute commit b99ee024a01a — awaiting tagged release

https://github.com/jaw187/node-traceroute/commit/b99ee024a01a40d3d20a92ad3769cc78a3f6386f
generic

#infosec #cybersecurity #dataprotection #npm #informationsecurity | OP Innovate

https://www.linkedin.com/posts/op-innovate_shell-command-injection-through-traceroute-activity-6678956453086191616-Rcpy
generic🔴 Active Exploitation

Shell Command Injection in traceroute | CVE-2018-21268 | Snyk

https://snyk.io/vuln/npm:traceroute:20160311

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmtraceroute—ghsa

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
traceroute———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 50× 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-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:42 UTCEPSS rescore
  5. 2026-07-07 13:42 UTCEPSS rescore
  6. 2026-07-06 16:24 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 02:20 UTCEPSS rescore
  9. 2026-07-05 02:27 UTCEPSS rescore
  10. 2026-07-04 06:28 UTCEPSS rescore
  11. 2026-07-04 06:28 UTCEPSS rescore
  12. 2026-07-02 16:54 UTCEPSS rescore
  13. 2026-07-01 16:01 UTCOSV refresh
  14. 2026-07-01 15:03 UTCEPSS rescore
  15. 2026-07-01 15:03 UTCEPSS rescore
  16. 2026-06-30 23:20 UTCEPSS rescore
  17. 2026-06-30 23:19 UTCEPSS rescore
  18. 2026-06-29 14:03 UTCEPSS rescore
  19. 2026-06-28 14:04 UTCEPSS rescore
  20. 2026-06-28 04:53 UTCEPSS rescore
  21. 2026-06-28 04:53 UTCEPSS rescore
  22. 2026-06-27 03:06 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-25 13:47 UTCEPSS rescore
Show 55 more
  1. 2026-06-24 14:02 UTCEPSS rescore
  2. 2026-06-24 14:02 UTCEPSS rescore
  3. 2026-06-23 21:30 UTCEPSS rescore
  4. 2026-06-23 21:30 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-22 14:23 UTCEPSS rescore
  7. 2026-06-21 14:54 UTCEPSS rescore
  8. 2026-06-21 14:54 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-19 19:23 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-18 17:50 UTCEPSS rescore
  15. 2026-06-17 17:50 UTCEPSS rescore
  16. 2026-06-17 17:50 UTCEPSS rescore
  17. 2026-06-16 17:50 UTCEPSS rescore
  18. 2026-06-16 17:50 UTCEPSS rescore
  19. 2026-06-15 17:45 UTCEPSS rescore
  20. 2026-06-14 23:15 UTCEPSS rescore
  21. 2026-06-14 23:14 UTCEPSS rescore
  22. 2026-06-14 00:13 UTCOSV refresh
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:09 UTCEPSS rescore
  25. 2026-06-12 23:09 UTCEPSS rescore
  26. 2026-06-11 13:57 UTCEPSS rescore
  27. 2026-06-10 22:16 UTCEPSS rescore
  28. 2026-06-10 13:19 UTCEPSS rescore
  29. 2026-06-08 14:14 UTCEPSS rescore
  30. 2026-06-08 14:14 UTCEPSS rescore
  31. 2026-06-07 15:22 UTCEPSS rescore
  32. 2026-06-07 15:22 UTCEPSS rescore
  33. 2026-06-06 13:45 UTCEPSS rescore
  34. 2026-06-06 13:45 UTCEPSS rescore
  35. 2026-06-05 22:45 UTCEPSS rescore
  36. 2026-06-05 22:45 UTCEPSS rescore
  37. 2026-06-05 06:08 UTCEPSS rescore
  38. 2026-06-05 06:08 UTCEPSS rescore
  39. 2026-06-04 13:10 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-01 13:50 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-05-31 22:29 UTCEPSS rescore
  45. 2026-05-31 00:14 UTCEPSS rescore
  46. 2026-05-31 00:14 UTCEPSS rescore
  47. 2026-05-29 13:41 UTCEPSS rescore
  48. 2026-05-28 13:42 UTCEPSS rescore
  49. 2026-05-28 13:42 UTCEPSS rescore
  50. 2026-05-27 13:38 UTCEPSS rescore
  51. 2026-05-27 13:38 UTCEPSS rescore
  52. 2026-05-27 01:58 UTCEG score recompute
  53. 2026-05-27 01:58 UTCGHSA enrichment
  54. 2026-05-26 13:42 UTCEPSS rescore
  55. 2026-05-26 13:42 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2018-21268?
CVE-2018-21268 is a critical vulnerability published on June 25, 2020. The traceroute (aka node-traceroute) package through 1.0.0 for Node.js allows remote command injection via the host parameter. This occurs because the Child.exec() method, which is considered to be not entirely safe, is used. In particular, an OS command can be placed after a newline character.
When was CVE-2018-21268 disclosed?
CVE-2018-21268 was first published in the National Vulnerability Database on June 25, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-21268 actively exploited?
CVE-2018-21268 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 90.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-21268?
CVE-2018-21268 has a CVSS v3 base score of 10.0 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2018-21268?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-21268, 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-21268

Explore →

Is Your Infrastructure Affected by CVE-2018-21268?

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

Start Free Scan →Browse All CVEs