| Package | Affected versions | Patched versions |
|---|---|---|
| inngest | ≥ 3.22.0, < 3.54.0 | 3.54.0 |
| inngest | ≥ 3.22.0, < 3.54.0 | 3.54.0 |
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.
An application is vulnerable if all of the following are true:
inngest SDK version >= 3.22.0, <= 3.53.1 (inclusive)serve() endpoint is reachable via PATCH, OPTIONS, or DELETE requests.Please check your framework's implementation for the serve handler (documentation) to asses whether it handles these HTTP methods. Common vulnerable configurations include:
app.use('/api/inngest', serve(...)), which routes PATCH and OPTIONS to the handler by default.The following are not affected:
GET, POST, and PUT.connect worker method.< 3.22.0 and >= 3.54.0, including all 4.x releases.The vulnerability was responsibly disclosed by an Inngest user. At this time, there are no known reports of exploitation.
[email protected] or later. The fix is backwards compatible with the 3.x release line. The 4.x line is also unaffected.process.env) within affected environments including Inngest signing keys and event keysserve endpoints using the PATCH, OPTIONS, DELETE http methods to assess if any environment variables may have been exposed.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
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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free