CVE-2026-42047

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-28441 (ENISA EUVD)Source: ENISA EUVD

8.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-26). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 7, 2026

Last Modified

October 26, 2026

Advisory Details (2)

Auto-updated May 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Inngest TypeScript SDK exposes environment variables via serve() handler on unhandled HTTP methods · Advisory · inngest/inngest-js · GitHub

https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx
Web page

Release [email protected] · inngest/inngest-js · GitHub

https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
inngest—
  • 3.22.0 up to 3.54.0: fixed in 3.54.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 37× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 197 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 97 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-10-26 20:28 UTCEG score recompute
  5. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-25 14:29 UTCEG score recompute
  8. 2026-10-24 17:37 UTCEG score recompute
  9. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-18 03:41 UTCEG score recompute
  17. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-17 14:30 UTCEG score recompute
  19. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-12 16:07 UTCEG score recompute
  25. 2026-10-11 19:49 UTCEG score recompute
Show 75 more
  1. 2026-10-11 17:03 UTCEG score recompute
  2. 2026-10-11 14:29 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-09-30 08:41 UTCOSV refresh
  15. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-11 15:23 UTCOSV refresh
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  30. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  32. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  33. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  34. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  42. 2026-08-23 19:33 UTCEG score recompute
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-08-17 12:42 UTCEG score recompute
  50. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  51. 2026-08-16 04:42 UTCEG score recompute
  52. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  53. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  54. 2026-08-14 03:17 UTCEG score recompute
  55. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  56. 2026-08-12 16:52 UTCEG score recompute
  57. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  58. 2026-08-11 15:54 UTCEG score recompute
  59. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  60. 2026-08-11 01:24 UTCEG score recompute
  61. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  62. 2026-08-09 14:57 UTCEG score recompute
  63. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  64. 2026-08-09 02:28 UTCEG score recompute
  65. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  66. 2026-08-08 02:45 UTCEG score recompute
  67. 2026-08-07 01:48 UTCEG score recompute
  68. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  69. 2026-08-05 22:13 UTCEG score recompute
  70. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  71. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  73. 2026-08-03 19:36 UTCEG score recompute
  74. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  75. 2026-08-02 04:29 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42047?
CVE-2026-42047 is a high-severity vulnerability; its CVE record was published on May 7, 2026. 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…
When was the CVE record for CVE-2026-42047 published?
The CVE record for CVE-2026-42047 was published on May 7, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-42047 actively exploited?
CVE-2026-42047 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42047?
CVE-2026-42047 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-42047?
A fix for CVE-2026-42047 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42047

Explore →

Is Your Infrastructure Affected by CVE-2026-42047?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs