CVE-2026-42047
Unauthenticated env var leakage via Inngest serve() endpoint (v3.22.0–v3.53.1).
Is CVE-2026-42047 being exploited?
Not confirmed. CVE-2026-42047 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-42047?
CVE-2026-42047 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-42047?
Yes. A fix has been recorded for CVE-2026-42047. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-42047 affect?
CVE-2026-42047 affects Inngest platform (v3.22.0–v3.53.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-42047?
Upgrade to 3.54.0 or restrict serve() methods at proxy
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exposes host environment variables (secrets/keys) via HTTP responses; attacker can read env vars via GET/POST/PUT on the serve() endpoint.
Patch when possible
- affected>= 3.22.0 and < 3.54.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.