LiveActive security incident?Get immediate response
CVE Record

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

A prototype pollution vulnerability was found in node.extend <1.1.7, ~<2.0.1 that allows an attacker to inject arbitrary properties onto Object.prototype.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-16491 affects the Node.js package node.extend. Vulnerable versions can let attacker-controlled data add properties to JavaScript’s global Object prototype, potentially changing application behavior. Business risk depends on whether the package is present and exposed to untrusted input.

Executive priority

Treat as a dependency hygiene issue with moderate urgency. Prioritize verification where Node.js services accept external input or support critical business workflows. No cited source indicates known active exploitation.

Technical view

The issue is prototype pollution in node.extend versions <1.1.7 and 2.x before 2.0.1, allowing arbitrary properties to be injected onto Object.prototype. The CVE record lists CWE-400 and provides no CVSS score in the supplied sources.

Likely exposure

Exposure is most likely in Node.js applications that directly or transitively depend on affected node.extend versions and process untrusted object data through it.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Practical impact depends on application logic and whether polluted prototype properties influence security decisions, data handling, or availability.

Researcher notes

Evidence is limited to the CVE record and HackerOne reference. The record identifies affected version ranges and prototype pollution impact, but does not provide CVSS, exploit maturity, or detailed remediation notes beyond implied fixed versions.

Mitigation direction

  • Upgrade node.extend outside the affected ranges: 1.1.7 or later, or 2.0.1 or later.
  • Review vendor and package maintainer guidance before release changes.
  • Rebuild and redeploy applications after dependency updates.
  • Prioritize internet-facing services and services processing untrusted JSON or object input.

Validation and detection

  • Check package manifests and lockfiles for node.extend versions.
  • Identify transitive dependencies that include node.extend.
  • Confirm deployed artifacts match remediated dependency versions.
  • Test application behavior after upgrade for regression risk.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-16491 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnenode.extend<1.1.7, ~<2.0.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.