node.extend vulnerabilities and fixes

Q: How do I fix node.extend vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Q: Is node.extend being exploited right now?

None of the tracked node.extend CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Q: Which node.extend CVE should I patch first?

CVE-2018-16491 currently ranks highest (64/100): A prototype pollution vulnerability was found in node.extend <1.1.7, ~<2.0.1 that allows an attacker to inject.

Recent CVEs affecting node.extend, with upgrade or downgrade steps. 1 tracked.

Also searched as: node extend, nodeextend.

node.extend has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-02-01. Highest priority: CVE-2018-16491 (score 64/100).

CVE-2018-16491 CRITICAL 9.8 UPGRADE A prototype pollution vulnerability was found in node.extend <1.1.7, ~<2.0.1 that allows an attacker to inject

FAQ

How do I fix node.extend vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is node.extend being exploited right now?

None of the tracked node.extend CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which node.extend CVE should I patch first?

CVE-2018-16491 currently ranks highest (64/100): A prototype pollution vulnerability was found in node.extend <1.1.7, ~<2.0.1 that allows an attacker to inject.

← Back to latest CVEs