npmWorst: Critical3 advisories

set-in: known vulnerabilities

set-in has 3 reviewed security advisories in the GitHub Advisory Database — 3 critical. The most recent was published 2026-02-11. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the set-in versions running across your servers, containers and images, and ranks what to patch first.

How to fix set-in

Upgrade set-in to a release at or above the fixed version shown for each advisory below. For npm:

npm install set-in@2.0.5 (or run npm audit fix)

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (3)

set-in Affected by Prototype Pollution Critical CWE-1321 — Affected: from 2.0.1 up to 2.0.5. Fixed in 2.0.5. Published 2026-02-11. GHSA-2c4m-g7rx-63q7 · CVE-2026-26021

Find set-in across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.