CVE-2026-26021: Set in Set-in Affected By Prototype Pollution Vulnerability

CRITICAL
Advisory Identifier: GHSA-2c4m-g7rx-63q7
CWE-1321
Published
Advisory Summary

CVE-2026-26021 is a CRITICAL set-in affected by prototype pollution vulnerability (CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')) affecting Set in libraries in the npm ecosystem. The issue involves set-in affected by prototype pollution. Remediation is available by upgrading affected packages to version 2.0.5.

CVE-2026-26021 at a Glance

CVE Identifier CVE-2026-26021
GHSA Identifier GHSA-2c4m-g7rx-63q7
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Affected Product Set in
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-26021

To remediate this vulnerability, upgrade all affected Set in dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

set-in fixed: 2.0.5
npm install set-in@2.0.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls set-in

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-26021, inspect your project dependencies using npm:

npm ls set-in

Analyze the terminal output to locate any version of Set in in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.0.5), your application is affected.

Note: The npm ls set-in command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'), where the product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype. In Set in, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A prototype pollution vulnerability exists in the the npm package set-in (>=2.0.1). Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. This has been fixed in version 2.0.5. ### Details The vulnerability resides in line 28 of https://github.com/ahdinosaur/set-in/blob/master/index.js where includes() function is used to check whether user provided input contain forbidden strings. ### PoC #### Steps to reproduce 1. Install latest version of set-in using npm install or cloning from git 2. Run the following code snippet: ```javascript Array.prototype.includes = () => false; const si = require('set-in'); const obj = {}; console.log({}.polluted); si(obj, [ 'constructor', 'prototype', 'polluted' ], 'yes'); console.log('{ ' + obj.polluted + ', ' + 'yes' + ' }'); // prints yes -> indicating that the patch was bypassed and prototype pollution occurred ``` #### Expected behavior Prototype pollution should be prevented and {} should not gain new properties. This should be printed on the console: ``` undefined undefined OR throw an Error ``` #### Actual behavior Object.prototype is polluted This is printed on the console: ``` undefined yes ``` ### Impact This is a prototype pollution vulnerability, which can have severe security implications depending on how set-in is used by downstream applications. Any application that processes attacker-controlled input using this package may be affected. It could potentially lead to the following problems: 1. Authentication bypass 2. Denial of service 3. Remote code execution (if polluted property is passed to sinks like eval or child_process)

CVE-2026-26021 Affected Set in Versions

1 component(s)
Fixed Versions:
2.0.5
Product / Package Ecosystem Affected Versions Fixed Version
set-in
npm
≥ 2.0.1
< 2.0.5
2.0.5

References

Frequently Asked Questions

What is CVE-2026-26021?
CVE-2026-26021 is a security vulnerability in Set in involving set-in Affected by Prototype Pollution under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution').
Which Set in versions are affected?
Affected versions include releases prior to 2.0.5 across affected packages: set-in.
What version fixes CVE-2026-26021?
Upgrading to 2.0.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is set-in affected?
Yes, set-in is affected in releases prior to 2.0.5. Upgrade your dependency to 2.0.5 or later.
What CWE is associated with CVE-2026-26021?
CVE-2026-26021 is classified under CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') (The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.).
How can I check npm dependencies for CVE-2026-26021?
Run the dependency tree command: 'npm ls set-in'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2c4m-g7rx-63q7",
  "modified" : "2026-02-12T14:19:12Z",
  "published" : "2026-02-11T15:13:28Z",
  "aliases" : [ "CVE-2026-26021" ],
  "summary" : "set-in Affected by Prototype Pollution",
  "details" : "### Summary\nA prototype pollution vulnerability exists in the the npm package set-in (>=2.0.1). Despite a previous fix that attempted to mitigate prototype pollution by checking whether user input contained a forbidden key, it is still possible to pollute Object.prototype via a crafted input using Array.prototype. This has been fixed in version 2.0.5.\n\n### Details\nThe vulnerability resides in line 28 of https://github.com/ahdinosaur/set-in/blob/master/index.js where includes() function is used to check whether user provided input contain forbidden strings.\n\n### PoC\n#### Steps to reproduce\n1. Install latest version of set-in using npm install or cloning from git\n2. Run the following code snippet:\n\n```javascript\nArray.prototype.includes = () => false; \nconst si = require('set-in');\nconst obj = {};\nconsole.log({}.polluted);\nsi(obj, [\n    'constructor',\n    'prototype',\n    'polluted'\n], 'yes');\nconsole.log('{ ' + obj.polluted + ', ' + 'yes' + ' }');  // prints yes -> indicating that the patch was bypassed and prototype pollution occurred\n```\n\n#### Expected behavior\nPrototype pollution should be prevented and {} should not gain new properties.\nThis should be printed on the console:\n```\nundefined\nundefined OR throw an Error\n```\n\n#### Actual behavior\nObject.prototype is polluted\nThis is printed on the console:\n```\nundefined \nyes\n```\n\n### Impact\nThis is a prototype pollution vulnerability, which can have severe security implications depending on how set-in is used by downstream applications. Any application that processes attacker-controlled input using this package may be affected.\nIt could potentially lead to the following problems:\n1. Authentication bypass\n2. Denial of service\n3. Remote code execution (if polluted property is passed to sinks like eval or child_process)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "set-in"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.1"
      }, {
        "fixed" : "2.0.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/security/advisories/GHSA-2c4m-g7rx-63q7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-26021"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/pull/6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/commit/34842cc02de3fd65d6f8bd0b268347e7b390125b"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/commit/6bad255961d379e4b1f5fbc52ef9dc8420816f24"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/commit/b8e1dabfdbd35c8d604b6324e01d03f280256c3d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ahdinosaur/set-in/commit/d87c1a09fa2edb55cd76440a67d83d1cb828df11"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ahdinosaur/set-in"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1321" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-11T15:13:28Z",
    "nvd_published_at" : "2026-02-11T22:15:52Z"
  }
}