Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-42047 high CVSS 8.6

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.

AI summary snake-internal / snake-material-v2

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.
❓ What is the problem
**information disclosure** (CWE-200) exists in inngest. Attackers reach the vulnerable code path via ``GET`` without authentication.
📍 Affected scope
inngest — . Attack surface: `GET` / `POST` / `PUT` / `PATCH`.
🔥 Severity
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.54.0**.
🛡️ Workaround
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`.
🔍 Detection
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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'inngest' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `inngest` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply 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 only `GET`, `POST`, and `PUT`. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade inngest to 3.54.0

    ステージング環境で 3.54.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm inngest
[{"type":"SEMVER","events":[{"introduced":"3.22.0"},{"fixed":"3.54.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →