Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-2c4m-g7rx-63q7 | set-in Affected by Prototype Pollution |
Fri, 13 Feb 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Set-in Project
Set-in Project set-in |
|
| CPEs | cpe:2.3:a:set-in_project:set-in:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Set-in Project
Set-in Project set-in |
|
| Metrics |
cvssV3_1
|
Thu, 12 Feb 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 12 Feb 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ahdinosaur
Ahdinosaur set-in |
|
| Vendors & Products |
Ahdinosaur
Ahdinosaur set-in |
Wed, 11 Feb 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | set-in provides the set value of nested associative structure given array of keys. A prototype pollution vulnerability exists in the the npm package set-in (>=2.0.1, < 2.0.5). 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. | |
| Title | Prototype pollution in set-in | |
| Weaknesses | CWE-1321 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-12T21:16:04.618Z
Reserved: 2026-02-09T21:36:29.554Z
Link: CVE-2026-26021
Updated: 2026-02-12T21:15:58.717Z
Status : Analyzed
Published: 2026-02-11T22:15:52.077
Modified: 2026-02-13T21:43:27.900
Link: CVE-2026-26021
No data.
OpenCVE Enrichment
Updated: 2026-04-17T20:15:27Z
Github GHSA