CVE-2018-7160

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 9.9%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass same-origin-policy checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
9.9%
EPSS %ILE
95th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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

May 17, 2018

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
Patch available.
generic

myF5

https://support.f5.com/csp/article/K63025104?utm_source=f5support&amp%3Butm_medium=RSS
generic

Node.js — March 2018 Security Releases

https://nodejs.org/en/blog/vulnerability/march-2018-security-releases/

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunodejs (4.2.6~dfsg-1ubuntu4.2+esm1) @ xenial2026-10-08ubuntu
redhatrh-nodejs8-nodejs-0:8.11.4-1.el72018-10-18redhat
npmnode-inspector—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

(21 across 21 ecosystems)
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.8(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.0-r0: fixed in 8.11.0-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.1~dfsg-2: fixed in 8.11.1~dfsg-2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.1~dfsg-2: fixed in 8.11.1~dfsg-2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.1~dfsg-2: fixed in 8.11.1~dfsg-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 8.11.1~dfsg-2: fixed in 8.11.1~dfsg-2
—

Weakness Classification(2)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 30× 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 168 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2018-7160?
CVE-2018-7160 is a high vulnerability published on May 17, 2018. The Node.js inspector, in 6.x and later is vulnerable to a DNS rebinding attack which could be exploited to perform remote code execution. An attack is possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the…
When was CVE-2018-7160 disclosed?
CVE-2018-7160 was first published on May 17, 2018, with the most recent update on October 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-7160 actively exploited?
CVE-2018-7160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.9% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-7160?
CVE-2018-7160 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2018-7160?
A fix for CVE-2018-7160 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2018-7160?

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

Book a Demo →Browse All CVEs