Most recent entries from all

EUVD-2026-309134

2026-10-07T10:11:37.763859+00:00

EUVD-2026-309134

fkie_cve-2026-42047

2026-10-07T10:11:37.763904+00:00

Inngest is a platform for running event-driven and scheduled background functions with queueing, retries, and step orchestration. Versions 3.22.0 through 3.53.1 contain a vulnerability that 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 its serve() endpoint is reachable via PATCH, OPTIONS, or DELETE requests, which is common in setups like Next.js Pages Router or Express's app.use(...). Not affected are Next.js App Router handlers that export only GET, POST, and PUT, and applications using the connect worker method. This issue has been fixed in version 3.54.0. To work around this issue 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.

GHSA-2jf5-6wwv-vhxx — Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods

2026-10-07T10:11:37.763949+00:00

Affected: npm: inngest

# 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 `inngest` SDK version `>= 3.22.0, <= 3.53.1` (inclusive) - Its `serve()` endpoint is reachable via `PATCH`, `OPTIONS`, or `DELETE` requests.

Please check your framework's implementation for the serve handler ([documentation](https://www.inngest.com/docs/learn/serving-inngest-functions)) 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 routes `PATCH` and `OPTIONS` to the handler by default.

The following are **not** affected:

- Next.js App Router handlers that explicitly export only `GET`, `POST`, and `PUT`. - Applications using the `connect` worker method. - SDK versions `< 3.22.0` and `>= 3.54.0`, including all `4.x` releases.…