LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28860: In Node.js mixme, prior to v0.5.1, an attacker can add or alter properties of an object via '__proto__' thr...

In Node.js mixme, prior to v0.5.1, an attacker can add or alter properties of an object via '__proto__' through the mutate() and merge() functions. The polluted attribute will be directly assigned to every object in the program. This will put the availability of the program at risk causing a potential denial of service (DoS).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-28860 affects the Node.js mixme package before v0.5.1. Unsafe object merging can let attacker-controlled data change shared object behavior across an application, creating denial-of-service risk. The source bundle does not provide CVSS, confirmed affected downstream products, or evidence of active exploitation.

Executive priority

Prioritize remediation for internet-facing or data-ingesting Node.js services using mixme before v0.5.1. Treat as a targeted dependency hygiene and availability-risk issue, not as confirmed mass exploitation based on the provided evidence.

Technical view

mixme before v0.5.1 allows prototype pollution through __proto__ handling in mutate() and merge(). A polluted attribute may be assigned broadly to objects in the running program, risking availability impact. The cited fix is associated with the upstream commit and the v0.5.1 boundary.

Likely exposure

Exposure is most likely in Node.js applications or bundled products that depend on mixme before v0.5.1 and pass untrusted object data into mutate() or merge(). The bundle lists NetApp and upstream references but does not identify specific affected NetApp products.

Exploitation context

No provided source and no KEV status support active exploitation. The issue is a prototype pollution class vulnerability, so practical impact depends on whether attacker-controlled object keys can reach vulnerable merge paths and whether polluted properties affect application control flow or availability.

Researcher notes

Evidence is strongest for upstream mixme before v0.5.1 and the prototype pollution mechanism in mutate() and merge(). The bundle lacks CVSS, CWE mapping, exploit telemetry, and detailed downstream product impact, so validation should focus on dependency presence and reachable data flow.

Mitigation direction

  • Upgrade mixme to v0.5.1 or later where feasible.
  • Review vendor advisories for bundled or transitive dependency exposure.
  • Block untrusted object keys from reaching merge or mutate paths.
  • Pin and rebuild dependencies after confirming the resolved version.
  • Monitor upstream GitHub advisory and NetApp advisory updates.

Validation and detection

  • Search dependency manifests and lockfiles for mixme versions before v0.5.1.
  • Confirm whether vulnerable functions process externally supplied objects.
  • Check software composition analysis results for CVE-2021-28860 or GHSA-79jw-6wg7-r9g4.
  • Verify production builds include the upgraded dependency version.
  • Review application error and availability telemetry for unexplained DoS symptoms.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

cve · low confidence lookup

CVE-2021-28860 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
3Timeline events
1ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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