{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7160 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-7160 is a high-severity server-side request forgery vulnerability in Nodejs Node.js, published on 17 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-7160 and fix it if it is affected.\n\nWhat it is: CVE-2018-7160 is a high-severity server-side request forgery vulnerability in Nodejs Node.js, published on 17 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-7160 in the wild and no public exploit code.\n\nAffected product: Nodejs Node.js. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-7160/ (Markdown: https://insights.sbomify.com/CVE-2018-7160/index.md)","id":"CVE-2018-7160","markdown":"https://insights.sbomify.com/CVE-2018-7160/index.md","name":"CVE-2018-7160","record":{"aliases":["ALPINE-CVE-2018-7160","CLEANSTART-2026-EN95904","CLEANSTART-2026-YQ27190","DEBIAN-CVE-2018-7160","UBUNTU-CVE-2018-7160"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js runtime","requires_auth":"none","summary":"Attackers can exploit DNS rebinding to access the Node.js inspector and execute arbitrary code if the debug port is active.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"nodejs","cpe":[{"product":"node.js","vendor":"nodejs"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-350","name":"Reliance on Reverse DNS Resolution for a Security-Critical Action"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Server-side request forgery in Node.js","id":"CVE-2018-7160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"nodejs:node.js","products":["nodejs:node.js"],"type":"ssrf","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in Node.js","id":"CVE-2018-7161"},"packages":[],"prev":{"headline":"Other in Node.js","id":"CVE-2018-7159"},"products":["Node.js"],"published":"2018-05-17","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Node","id":"CVE-2023-32002","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2016-6303","kev_date_added":null,"published":"2016-09-16"},{"cvss_score":9.1,"headline":"Security feature bypass in Node.js","id":"CVE-2017-15896","kev_date_added":null,"published":"2017-12-11"},{"cvss_score":8.1,"headline":"Misconfiguration in Node.js","id":"CVE-2018-12120","kev_date_added":null,"published":"2018-11-28"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21891","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":7.9,"headline":"Path traversal in Node","id":"CVE-2024-21896","kev_date_added":null,"published":"2024-02-20"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["The Node.js Project"]},"summary":"Attackers can exploit DNS rebinding to access the Node.js inspector and execute arbitrary code if the debug port is active.","url":"https://insights.sbomify.com/CVE-2018-7160/"}