CVE-2026-42047

Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods

HIGH
8.6
CVSS Score
Published: May 7, 2026 at 08:38 PM UTC
Updated: October 26, 2026 at 08:10 PM UTC
2 products affected across 1 vendorInngestJs

Using inngest-js by inngest?

Get instant alerts when new vulnerabilities affect inngest-js - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.6
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.22.0 ≤ v < 3.54.0
3.22.0 ≤ v < 3.54.0
Affected range stops below 3.54.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (2)

x_refsource_CONFIRMMitigationVendor Advisory
Source: cverecord
https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx
x_refsource_MISCPatchProduct
Source: cverecord
https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.6HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-200CWE-497

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card