# CVE-2026-42047: Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods

> Unauthenticated attackers can exfiltrate environment variables and secrets from the host process by sending unsupported HTTP methods to the serve() handler.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-2jf5-6wwv-vhxx

## What is CVE-2026-42047?

CVE-2026-42047 is a high-severity vulnerability in inngest-js, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-42047?

2 open source packages ship an affected version, including inngest. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `inngest` | npm | From 3.22.0 | 3.54.0 |
| `inngest` | npm | From 3.22.0 | 3.54.0 |

Products: Inngest Inngest.

## How do I fix CVE-2026-42047?

Upgrade inngest to 3.54.0 or later.

## Is CVE-2026-42047 being exploited?

There is no known exploitation of CVE-2026-42047 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42047 and fix it if it is affected.

What it is: CVE-2026-42047 is a high-severity vulnerability in inngest-js, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42047 in the wild and no public exploit code.

Affected packages and fixed versions:
- inngest (npm): affected from 3.22.0; fixed in 3.54.0
- inngest (npm): affected from 3.22.0; fixed in 3.54.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42047/ (Markdown: https://insights.sbomify.com/CVE-2026-42047/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42047
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42047
- OSV: https://osv.dev/vulnerability/CVE-2026-42047

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42047/
Summaries are generated and may contain mistakes; the official description above is the record.