Inngest Js
Approved changes feed: RSS · Atom
cpe:2.3:a:inngest:inngest-js:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Inngest (cef18f01-9f03-5d2a-bd09-8b4665e03531) |
|---|---|
| Product | Inngest Js (9df1a71d-1411-58a4-a813-3f7994f04eec) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/inngest/inngest-js |
purl2cpe | 2026-06-01 10:10:56.268629 |
pkg:npm/inngest |
purl2cpe | 2026-06-01 10:10:56.268631 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-42047 |
vulnerable | 2026-06-08 08:03:15.885338 |
Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods
HIGH (8.6)
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.
Published: 2026-05-07T20:38:36.171Z
Updated: 2026-05-08T13:52:50.549Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.