CVE-2026-42047

{"id": "CVE-2026-42047", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-42047", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-05-08T13:52:40.509395Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.6, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.0, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "inngest", "product": "inngest-js", "versions": [{"status": "affected", "version": ">= 3.22.0, < 3.54.0"}]}]}], "published": "2026-05-07T21:16:29.980", "references": [{"url": "https://github.com/inngest/inngest-js/releases/tag/inngest%403.54.1", "tags": ["Patch", "Product"], "source": "security-advisories@github.com"}, {"url": "https://github.com/inngest/inngest-js/security/advisories/GHSA-2jf5-6wwv-vhxx", "tags": ["Mitigation", "Vendor Advisory"], "source": "security-advisories@github.com"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-200"}, {"lang": "en", "value": "CWE-497"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "Inngest es una plataforma para ejecutar funciones en segundo plano impulsadas por eventos y programadas con encolamiento, reintentos y orquestaci\u00f3n de pasos. Las versiones 3.22.0 a 3.53.1 contienen una vulnerabilidad que permite a atacantes remotos no autenticados exfiltrar variables de entorno del proceso anfitri\u00f3n a trav\u00e9s del gestor HTTP \u2019serve()\u2019. El gestor \u2019serve()\u2019 implementa los m\u00e9todos GET, POST y PUT. Las solicitudes que utilizan PATCH, OPTIONS o DELETE pasan a un gestor gen\u00e9rico que devuelve informaci\u00f3n de diagn\u00f3stico. Un cambio introducido en la v3.22.0 hizo que esta respuesta de diagn\u00f3stico incluyera el contenido de \u2019process.env\u2019, exponiendo cualquier secreto, claves API o credenciales presentes en el entorno. Una aplicaci\u00f3n es vulnerable si su punto final \u2019serve()\u2019 es accesible a trav\u00e9s de solicitudes PATCH, OPTIONS o DELETE, lo cual es com\u00fan en configuraciones como Next.js Pages Router o \u2019app.use(...)\u2019 de Express. No se ven afectados los gestores de Next.js App Router que exportan solo GET, POST y PUT, y las aplicaciones que utilizan el m\u00e9todo de trabajador connect. Este problema ha sido solucionado en la versi\u00f3n 3.54.0. Para solucionar este problema si la actualizaci\u00f3n no es posible de inmediato, restrinja el punto final \u2019serve()\u2019 en la capa del framework o del proxy inverso para que acepte solo GET, POST y PUT. El punto final \u2019serve()\u2019 de Inngest no requiere ning\u00fan otro m\u00e9todo HTTP."}], "lastModified": "2026-10-26T20:10:00.160", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:inngest:inngest:*:*:*:*:*:node.js:*:*", "vulnerable": true, "matchCriteriaId": "B1AF5D1A-E672-4AFA-BC25-1EB6E2F08491", "versionEndExcluding": "3.54.0", "versionStartIncluding": "3.22.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com"}