inngest Known Vulnerabilities & Fixes
inngest has 1 known security vulnerability in npm (Node.js). Upgrade to version 3.54.0 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 3.54.0
Upgrading to 3.54.0 or later resolves all 1 known vulnerability in inngest. Run: npm install inngest@3.54.0
Is inngest in your project?
Check if you're affected and upgrade to 3.54.0 to stay secure.
Security Summary
- 1 affected version range has been identified across this advisory.
- 100% of known issue has a published fixed version.
- Remediation: npm update inngest
Vulnerabilities
1 unique vulnerability — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details.
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-42047 Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods | HIGH | All versions | 3.54.0 |
About This Data
Vulnerability data for inngest is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of inngest.