CVE-2026-42047 Details
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.
A vulnerability exists in the Inngest TypeScript SDK in versions 3.22.0 prior to 3.54.0. It allows unauthenticated remote attackers to exfiltrate environment variables from the host process through the serve() HTTP handler. This issue arises because the serve() handler, which supports GET, POST, and PUT methods, inadvertently exposes the contents of process.env in response to PATCH, OPTIONS, or DELETE requests. This exposure can include sensitive information such as secrets, API keys, or credentials. The vulnerability is present when the serve() endpoint is accessible via the aforementioned HTTP methods, a common scenario in applications using Next.js Pages Router or certain Express configurations.
Users should upgrade to Inngest version 3.54.0 or later. After upgrading, it is recommended to rotate any secrets that were present in environment variables within affected environments, including Inngest signing keys and event keys. Additionally, users should check logs for any requests to serve endpoints using PATCH, OPTIONS, or DELETE methods to assess if any environment variables may have been exposed. For those on platforms with long-lived deployments, such as Vercel or Cloudflare Workers, be aware that older deployments may still be vulnerable and consider using Vercel's deployment protection features to mitigate impact.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 8, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1 | [email protected] | PatchProduct |
| https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx | [email protected] | MitigationVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
| CWE-497 | Exposure of Sensitive System Information to an Unauthorized Control Sphere | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| inngest inngest | >= 3.22.0, < 3.54.0 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 26, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 13, 2026 | Initial Analysis | [email protected] |
| May 7, 2026 | New CVE Received | [email protected] |