GHSA-2jf5-6wwv-vhxx
HIGHGHSA-2jf5-6wwv-vhxx is a high-severity (CVSS 8.6) Information Exposure vulnerability in inngest. O3 Security confirms whether GHSA-2jf5-6wwv-vhxx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2jf5-6wwv-vhxx.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2jf5-6wwv-vhxx plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 356,453 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
inngestnpmDescription
Summary
A vulnerability in the Inngest TypeScript SDK versions 3.22.0 through 3.53.1 allows unauthenticated remote attackers to exfiltrate environment variables from the host process via the serve() HTTP handler.
The serve() handler implements GET, POST, and PUT methods. Requests using PATCH, OPTIONS, or DELETE fall through to a generic handler that returns diagnostic information. A change introduced in v3.22.0 caused this diagnostic response to include the contents of process.env, exposing any secrets, API keys, or credentials present in the environment.
Who is affected
An application is vulnerable if all of the following are true:
- It uses
inngestSDK version>= 3.22.0, <= 3.53.1(inclusive) - Its
serve()endpoint is reachable viaPATCH,OPTIONS, orDELETErequests.
Please check your framework's implementation for the serve handler (documentation) to asses whether it handles these HTTP methods. Common vulnerable configurations include:
- Next.js Pages Router, which forwards all HTTP methods to the handler.
- Express via
app.use('/api/inngest', serve(...)), which routesPATCHandOPTIONSto the handler by default.
The following are not affected:
- Next.js App Router handlers that explicitly export only
GET,POST, andPUT. - Applications using the
connectworker method. - SDK versions
< 3.22.0and>= 3.54.0, including all4.xreleases.
The vulnerability was responsibly disclosed by an Inngest user. At this time, there are no known reports of exploitation.
Remediation
- Upgrade to
[email protected]or later. The fix is backwards compatible with the3.xrelease line. The4.xline is also unaffected. - Rotate any secrets that were presence in environment variables (
process.env) within affected environments including Inngest signing keys and event keys - Search logs for any requests to your
serveendpoints using thePATCH,OPTIONS,DELETEhttp methods to assess if any environment variables may have been exposed.
Additional recommendations
Users on platforms with long-lived deployments (e.g. Vercel, Cloudflare Workers) should be aware that prior deployments remain reachable at their immutable URLs and may continue to expose the vulnerability even after a new deployment is promoted. For example, Vercel offers security features such as "Deployment Protection" and the ability to delete older deployments which can help immediately mitigate impact.
For additional security, users can also adjust firewall or proxy rules to only allow requests to their serve endpoint from Inngest IP addresses available here: http://inngest.com/ips-v4, http://inngest.com/ips-v6
Workarounds
If upgrading is not immediately possible, restrict the serve() endpoint at the framework or reverse-proxy layer to accept only GET, POST, and PUT. The Inngest serve() endpoint does not require any other HTTP methods.
Resources
- Rotating Inngest keys: https://www.inngest.com/docs/platform/manage/rotating-keys
- Inngest signing keys: https://www.inngest.com/docs/platform/signing-keys
- Inngest event keys: https://www.inngest.com/docs/events/creating-an-event-key
- Inngest security best practices: https://www.inngest.com/docs/learn/security
Credits
- Ben Hylak - an independent security researcher, discovered and responsibly disclosed the vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | inngest | ≥ 3.22.0&&< 3.54.0 | 3.54.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for inngest. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update inngest to 3.54.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2jf5-6wwv-vhxx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-2jf5-6wwv-vhxx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2jf5-6wwv-vhxx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2jf5-6wwv-vhxx in your dependencies?
O3 detects GHSA-2jf5-6wwv-vhxx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.