CVE-2026-42047: Inngest is a platform for running event-driven and scheduled background functions with queueing, retries, and

Q: How do I fix CVE-2026-42047?

inngest: upgrade to 3.54.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-42047 being exploited?

CVE-2026-42047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-42047 affect?

CVE-2026-42047 affects inngest. Severity is high (CVSS 8.6). 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

Q: How urgent is CVE-2026-42047?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.6REMOTEUPGRADE

CVE-2026-42047 is a high-severity flaw (CVSS 8.6) affecting inngest. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 handle

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.6 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 68%)
CISA exploited list	No
Weakness	CWE-200, CWE-497
Published	2026-05-07
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: inngest

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-07 21:16 UTCPublished CVE record published
2026-10-26 20:10 UTCUpdated Record last modified

inngest inngest UPGRADE

Affected: >= 3.22.0 and < 3.54.0

Fixed in: 3.54.0

Safe to downgrade to: a release before 3.22.0

1. Check installed version

npm ls inngest

2. UPGRADE to 3.54.0

npm install inngest@">=3.54.0"

3. If no update is available yet, DOWNGRADE to a release before 3.22.0

npm view inngest versions npm install inngest@"<3.22.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-42047?

inngest: upgrade to 3.54.0. Exact commands for each OS are on this page.

Is CVE-2026-42047 being exploited?

CVE-2026-42047 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-42047 affect?

CVE-2026-42047 affects inngest. Severity is high (CVSS 8.6). 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

How urgent is CVE-2026-42047?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

References

← Back to latest CVEs