{"id":"GHSA-2jf5-6wwv-vhxx","revision":null,"records":[{"revision":"f5447f0656124428ab2af47a91a91fab","observedAt":"2026-10-23T15:48:27.903+00:00","statement":{"source":"cve-program","id":"CVE-2026-42047","aliases":[],"title":"Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods","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.","state":0,"publishedAt":"2026-05-07T20:38:36.171+00:00","modifiedAt":"2026-05-08T13:52:50.549+00:00","affected":[{"ecosystem":"Vendor product","name":"inngest-js","ranges":[],"versions":[],"rawVersionEvidence":"{\n                    \"vendor\": \"inngest\",\n                    \"product\": \"inngest-js\",\n                    \"versions\": [\n                        {\n                            \"version\": \">= 3.22.0, < 3.54.0\",\n                            \"status\": \"affected\"\n                        }\n                    ]\n                }"}],"metrics":[{"system":"CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","score":8.6,"severity":"HIGH"}],"references":["https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx","https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1"],"sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-42047","license":"CVE Program Terms of Use","key":"cve-program:CVE-2026-42047","identifiers":["CVE-2026-42047"]},"retained":false,"historicalAffected":[]},{"revision":"049aa03fec834486b36e17fb57b6b58a","observedAt":"2026-11-01T07:11:31.94+00:00","statement":{"source":"euvd","id":"EUVD-2026-28441","aliases":["CVE-2026-42047","GHSA-2jf5-6wwv-vhxx"],"title":"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 exfiltr…","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.","state":0,"publishedAt":null,"modifiedAt":null,"affected":[],"metrics":[{"system":"EUVD CVSS 3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","score":8.6,"severity":null}],"references":["https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx","https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1"],"sourceUrl":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-28441","license":"ENISA EUVD · source terms and attribution apply","enrichment":{"sourceStatus":null,"weaknesses":[],"productCriteria":[],"sourceDates":{"datePublished":"May 7, 2026, 8:38:36 PM","dateUpdated":"May 8, 2026, 1:52:50 PM"},"relatedAdvisories":[],"note":"EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON."},"key":"euvd:EUVD-2026-28441","identifiers":["EUVD-2026-28441","CVE-2026-42047","GHSA-2jf5-6wwv-vhxx"]},"retained":false,"historicalAffected":[]},{"revision":"312606b0749643b1b158ae3febae7901","observedAt":"2026-10-27T11:12:01.124+00:00","statement":{"source":"nvd","id":"CVE-2026-42047","aliases":[],"title":"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 exfiltr…","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.","state":0,"publishedAt":"2026-05-07T21:16:29.98+00:00","modifiedAt":"2026-10-26T20:10:00.16+00:00","affected":[],"metrics":[{"system":"CVSS 3.1 · security-advisories@github.com · Secondary","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","score":8.6,"severity":"HIGH"}],"references":["https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1","https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx"],"sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-42047","license":"NIST NVD usage terms; underlying source attribution retained","enrichment":{"sourceStatus":"Analyzed","weaknesses":["CWE-200","CWE-497"],"productCriteria":["cpe:2.3:a:inngest:inngest:*:*:*:*:*:node.js:*:*"],"sourceDates":{"published":"2026-05-07T21:16:29.980","lastModified":"2026-10-26T20:10:00.160"},"relatedAdvisories":[],"note":"NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON."},"key":"nvd:CVE-2026-42047","identifiers":["CVE-2026-42047"]},"retained":false,"historicalAffected":[]},{"revision":"d210308241df45ec8eae136f49599f2b","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"GHSA-2jf5-6wwv-vhxx","aliases":["CVE-2026-42047"],"title":"Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods","description":"# Summary\n\nA vulnerability in the Inngest TypeScript SDK versions `3.22.0` through `3.53.1` allows unauthenticated remote attackers to exfiltrate environment variables from the host process via the `serve()` HTTP handler.\n\nThe `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.\n\n# Who is affected\n\nAn application is vulnerable if **all** of the following are true:\n\n- It uses `inngest` SDK version `>= 3.22.0, <= 3.53.1` (inclusive)\n- Its `serve()` endpoint is reachable via `PATCH`, `OPTIONS`, or `DELETE` requests.\n\nPlease check your framework's implementation for the serve handler ([documentation](https://www.inngest.com/docs/learn/serving-inngest-functions)) to asses whether it handles these HTTP methods. Common vulnerable configurations include:\n\n- Next.js Pages Router, which forwards all HTTP methods to the handler.\n- Express via `app.use('/api/inngest', serve(...))`, which routes `PATCH` and `OPTIONS` to the handler by default.\n\nThe following are **not** affected:\n\n- Next.js App Router handlers that explicitly export only `GET`, `POST`, and `PUT`.\n- Applications using the `connect` worker method.\n- SDK versions `< 3.22.0` and `>= 3.54.0`, including all `4.x` releases.\n\nThe vulnerability was responsibly disclosed by an Inngest user. At this time, there are no known reports of exploitation.\n\n# Remediation\n\n1. Upgrade to `inngest@3.54.0` or later. The fix is backwards compatible with the `3.x` release line. The `4.x` line is also unaffected.\n2. Rotate any secrets that were presence in environment variables (`process.env`) within affected environments including Inngest signing keys and event keys\n3. Search logs for any requests to your `serve` endpoints using the `PATCH`, `OPTIONS`, `DELETE` http methods to assess if any environment variables may have been exposed.\n\n## Additional recommendations\n\nUsers on platforms with long-lived deployments (e.g. Vercel, Cloudflare Workers) should be aware that prior deployments remain reachable at their immutable URLs and may continue to expose the vulnerability even after a new deployment is promoted. For example, Vercel offers security features such as \"[Deployment Protection](https://vercel.com/docs/deployment-protection#standard-protection)\" and [the ability to delete older deployments](https://vercel.com/kb/guide/how-do-i-delete-an-individual-deployment) which can help immediately mitigate impact.\n\nFor additional security, users can also adjust firewall or proxy rules to only allow requests to their `serve` endpoint from Inngest IP addresses available here: http://inngest.com/ips-v4, http://inngest.com/ips-v6\n\n### Workarounds\n\nIf 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.\n\n### Resources\n\n- Rotating Inngest keys: https://www.inngest.com/docs/platform/manage/rotating-keys\n- Inngest signing keys: https://www.inngest.com/docs/platform/signing-keys\n- Inngest event keys: https://www.inngest.com/docs/events/creating-an-event-key\n- Inngest security best practices: https://www.inngest.com/docs/learn/security\n\n### Credits\n\n- Ben Hylak - an independent security researcher, discovered and responsibly disclosed the vulnerability.","state":0,"publishedAt":"2026-05-05T18:13:52+00:00","modifiedAt":"2026-05-11T13:53:13.460971+00:00","affected":[{"ecosystem":"npm","name":"inngest","ranges":[{"type":"SEMVER","events":[{"kind":"introduced","version":"3.22.0"},{"kind":"fixed","version":"3.54.0"}]}],"versions":[],"rawVersionEvidence":null}],"metrics":[{"system":"CVSS_V3","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","score":null,"severity":null},{"system":"Publisher rating","vector":null,"score":null,"severity":"HIGH"}],"references":["https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx","https://nvd.nist.gov/vuln/detail/CVE-2026-42047","https://github.com/inngest/inngest-js","https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1","https://vercel.com/docs/deployment-protection#standard-protection","https://vercel.com/kb/guide/how-do-i-delete-an-individual-deployment","https://www.inngest.com/docs/events/creating-an-event-key","https://www.inngest.com/docs/learn/security","https://www.inngest.com/docs/learn/serving-inngest-functions","https://www.inngest.com/docs/platform/manage/rotating-keys","https://www.inngest.com/docs/platform/signing-keys"],"sourceUrl":"https://github.com/advisories/GHSA-2jf5-6wwv-vhxx","license":"GitHub Advisory Database · CC-BY-4.0","key":"osv:GHSA-2jf5-6wwv-vhxx","identifiers":["GHSA-2jf5-6wwv-vhxx","CVE-2026-42047"]},"retained":false,"historicalAffected":[]}],"coverage":[{"source":"cisa-kev:global","scope":"Complete CISA KEV catalog; all vendors. Missing entries do not establish absence of exploitation.","generation":"2026-11-02T16:59:10.1690873+00:00","complete":true,"records":1766,"lastAttemptAt":"2026-11-02T16:59:10.1690873+00:00","lastSuccessAt":"2026-11-02T16:59:10.3116254+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:59:10.3116261+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"cve-program","scope":"Official CVE Program baseline and cumulative hourly delta; all vendors, published and rejected records","generation":"cve-37087f5ac35d6d996bd0480d4228062695465d95096b336bdfd509d8efa3a1e5-84aaed8dccc4cedba653bef65981e073d8c5c12f4ff4b05530eb210ffb1705c4","complete":true,"records":417922,"lastAttemptAt":"2026-11-02T16:57:24.2192862+00:00","lastSuccessAt":"2026-11-02T16:57:24.1330437+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:57:24.2192862+00:00","snapshotPublishedAt":"2026-11-02T16:30:26+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"euvd","scope":"Rolling EUVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global EUVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-3afbfcfae1fe455bbc5a5006f95b2df4","complete":true,"records":13568,"lastAttemptAt":"2026-11-02T16:59:11.5322103+00:00","lastSuccessAt":"2026-11-02T11:59:30.621+00:00","error":null,"lastVerifiedAt":"2026-11-02T11:59:30.621+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13637,"expectedIdentifiers":13637,"failedIdentifiers":0},{"source":"first-epss:nuget","scope":"FIRST EPSS for explicit CVE aliases in the collected public NuGet archive. Not a global EPSS backfill.","generation":"2026-11-02T16:59:10.1690873+00:00","complete":true,"records":1095,"lastAttemptAt":"2026-11-02T16:59:10.1690873+00:00","lastSuccessAt":"2026-11-02T16:59:10.3123623+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:59:10.3123624+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"nvd","scope":"Rolling NVD lookups of CVE aliases in current public OSV archives; 500 identifiers per refresh, rechecked after 48 hours. Not a global NVD catalog. Successful not-found lookups count as checked; they do not imply withdrawal or safety. No reader inventory is sent.","generation":"enrichment-a52593857bad4381a86db8a8b44be613","complete":true,"records":13580,"lastAttemptAt":"2026-11-02T16:59:10.8868787+00:00","lastSuccessAt":"2026-11-02T15:57:47.378+00:00","error":null,"lastVerifiedAt":"2026-11-02T15:57:47.378+00:00","snapshotPublishedAt":null,"importing":false,"stagedRecords":0,"checkedIdentifiers":13637,"expectedIdentifiers":13637,"failedIdentifiers":0},{"source":"osv:Go","scope":"Complete OSV Go ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"go-21dcd6662970dfea02e4ea60ee637115e8d92664947484d2b9276b3f6568a84f","complete":true,"records":9815,"lastAttemptAt":"2026-11-02T16:59:09.9326132+00:00","lastSuccessAt":"2026-10-30T23:47:34.1817587+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:59:09.9326132+00:00","snapshotPublishedAt":"2026-10-30T23:33:17+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:NuGet","scope":"Complete OSV NuGet ecosystem archive, including GitHub Advisory Database records; NuGet version matching only","generation":"nuget-2de9ccc5290f060c7aa63f89c25dd76f655a64ba1aba7c05c97fa3bee4f09899","complete":true,"records":1967,"lastAttemptAt":"2026-11-02T16:57:24.3688876+00:00","lastSuccessAt":"2026-10-28T20:55:34.2982937+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:57:24.3688876+00:00","snapshotPublishedAt":"2026-10-28T20:03:08+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:crates.io","scope":"Complete OSV crates.io ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"crates.io-5eac0f41c5234939771ec81ee6dcecba911c3ba21e363f4cecd95fcede18b96b","complete":true,"records":3035,"lastAttemptAt":"2026-11-02T16:59:10.128203+00:00","lastSuccessAt":"2026-11-02T13:57:36.6498985+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:59:10.128203+00:00","snapshotPublishedAt":"2026-11-02T12:18:01+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null},{"source":"osv:npm","scope":"Complete OSV npm ecosystem archive, including withdrawn and malicious-package source records; statement counts are not unique CVE counts","generation":"npm-204813e4df71f7a2214cb16c924f482af6e49a4adf7efb0aebb0bd02e4e23b8c","complete":true,"records":231027,"lastAttemptAt":"2026-11-02T16:59:09.7642824+00:00","lastSuccessAt":"2026-11-02T16:59:08.3366694+00:00","error":null,"lastVerifiedAt":"2026-11-02T16:59:09.7642824+00:00","snapshotPublishedAt":"2026-11-02T16:33:40+00:00","importing":false,"stagedRecords":0,"checkedIdentifiers":null,"expectedIdentifiers":null,"failedIdentifiers":null}]}