Information Disclosure in inngest (CVE-2026-42047)
Summary
Vulnerability in inngest (CVE-2026-42047). Confidential information can be exposed externally. Exploitable via GET. Mitigation: upgrade to 3.54.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42047 has been found in inngest.
Attackers can target a specific entry point like GET over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade inngest to 3.54.0 or later.
If unsure, ask your IT team or search "inngest CVE-2026-42047" on the vendor's site.
CVE-2026-42047 (inngest) — CWE-200 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET / POST / PUT / PATCH
Patched: 3.54.0 — apply immediately
Workaround: If upgrading is not immediately possible, restrict the serve() endpoint at the framework or reverse-proxy layer to accept only GET, POST, and PUT.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in inngest. Attackers reach the vulnerable code path via GET without authentication.
Check the vendor advisory for the affected versions of inngest. Attack surface: GET / POST / PUT / PATCH.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 3.54.0.
Workaround: If upgrading is not immediately possible, restrict the serve() endpoint at the framework or reverse-proxy layer to accept only GET, POST, and PUT.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'inngest' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'inngest' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
inngestを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If upgrading is not immediately possible, restrict the `serve()` endpoint at the framework or reverse-proxy layer to accept only `GET`, `POST`, and `PUT`.パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, restrict the
serve()endpoint at the framework or reverse-proxy layer to accept onlyGET,POST, andPUT. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade inngest to 3.54.0ステージング環境で 3.54.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web vercel.com
- web vercel.com
- web inngest.com
- web inngest.com
- web inngest.com
- web inngest.com
- web inngest.com
- web github.com