inngest (npm) has 1 known vulnerability, the worst rated HIGH. Upgrade to 3.54.0 or later to clear it. No malicious-package signal is recorded.
23 direct dependencies
5 carry known advisories, worst HIGH
0 packages depend on it
an advisory here reaches each of them
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 33rd percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-2jf5-6wwv-vhxx, the advisory selected below
A vulnerability in the Inngest TypeScript SDK versions 3.22.0 through 3.53.1 allows unauthenticated remote attackers to exfiltrate environment variables from…
Full advisory text at GitHub advisory, NVD or OSV.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for inngest (npm), the worst rated HIGH, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 1 known vulnerability for inngest (npm), the worst rated HIGH. They are GHSA-2jf5-6wwv-vhxx.
3.54.0 or later clears every advisory recorded for inngest (npm). Check the release you pick before installing it.
Search inngest in CyberXYZ Check at https://cyberxyz.io/check?q=inngest. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 11:12 UTC. The most recent advisory here was published 2026-05-05. Updated continuously from NVD, GHSA, OSV and CNA feeds.