This page was not yet optimized for use on mobile devices.
CVE-2026-42047
Data
| Vulnerability ID | CVE-2026-42047 |
|---|---|
| Published on | 07.05.2026 21:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:inngest:inngest:3.22.0:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.1:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.2:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.3:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.4:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.5:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.6:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.7:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.8:*:*:*:*:node.js:*:*,
cpe:2.3:a:inngest:inngest:3.22.9:*:*:*:*:node.js:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.