{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "inngest"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.22.0"
            },
            {
              "fixed": "3.54.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42047"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200",
      "CWE-497"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-05T18:13:52Z",
    "nvd_published_at": "2026-05-07T21:16:29Z",
    "severity": "HIGH"
  },
  "details": "# 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 `\u003e= 3.22.0, \u003c= 3.53.1` (inclusive)\n- Its `serve()` endpoint is reachable via `PATCH`, `OPTIONS`, or `DELETE` requests.\n\nPlease check your framework\u0027s 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(\u0027/api/inngest\u0027, 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 `\u003c 3.22.0` and `\u003e= 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.",
  "id": "GHSA-2jf5-6wwv-vhxx",
  "modified": "2026-05-11T13:29:55Z",
  "published": "2026-05-05T18:13:52Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42047"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/inngest/inngest-js"
    },
    {
      "type": "WEB",
      "url": "https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1"
    },
    {
      "type": "WEB",
      "url": "https://vercel.com/docs/deployment-protection#standard-protection"
    },
    {
      "type": "WEB",
      "url": "https://vercel.com/kb/guide/how-do-i-delete-an-individual-deployment"
    },
    {
      "type": "WEB",
      "url": "https://www.inngest.com/docs/events/creating-an-event-key"
    },
    {
      "type": "WEB",
      "url": "https://www.inngest.com/docs/learn/security"
    },
    {
      "type": "WEB",
      "url": "https://www.inngest.com/docs/learn/serving-inngest-functions"
    },
    {
      "type": "WEB",
      "url": "https://www.inngest.com/docs/platform/manage/rotating-keys"
    },
    {
      "type": "WEB",
      "url": "https://www.inngest.com/docs/platform/signing-keys"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods"
}