8.6
/ 10
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description
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.
AI Analysis
Unauthenticated remote attackers can exfiltrate environment variables from the host process via the serve() HTTP handler due to a vulnerability in Inngest versions 3.22.0 through 3.53.1.
Basic Information
ID
CVE-2026-42047
Source
GitHub_M
Published
May 7, 2026 at 20:38
Affected Product
Vendor
inngest
Product
inngest-js
Version
>= 3.22.0, < 3.54.0
Affected Versions
inngest inngest-js >= 3.22.0, < 3.54.0
CWE Classification
AI Assessment
AI Score
8.6 / 10
AI Severity
High
Vendor
Inngest
Product
inngest-js
Version
3.22.0-3.53.1