GHSA-59h8-w5q6-mfmp
Trigger.dev: Unauthenticated Realtime Stream Data Injection via Run FriendlyId
Quick fix
GHSA-59h8-w5q6-mfmp — trigger.dev: upgrade to the fixed version with the command below.
npm install trigger.dev@4.5.5Details
## Summary
The POST handler for `/realtime/v1/streams/:runId/:streamId` has no authentication. Any entity that knows or guesses a run friendlyId can inject arbitrary data into its realtime stream.
## Vulnerability Details
**File:** `apps/webapp/app/routes/realtime.v1.streams.$runId.$streamId.ts`
The `action` handler (line 17) has no auth wrapper. The code comment says: "Plain action for backwards compatibility with older clients that don't send auth headers."
The run lookup at line 29 uses `where: { friendlyId: runId }` with NO environment scoping (`runtimeEnvironmentId` is not checked), so production runs are accessible.
Run friendlyIds follow predictable patterns (e.g., `run_1234abcd`).
## Steps to Reproduce
```bash # No authentication required curl -X POST "http://localhost:8030/realtime/v1/streams/run_KNOWN_ID/stream_1" -H "Content-Type: application/json" -d '{"injected": "data"}' ```
## Impact
Unauthenticated data injection into any run realtime stream. Cross-environment access (no scoping).
Are you affected?
Enter the version of the package you're using.
Affected packages
References
- https://github.com/triggerdotdev/trigger.dev/security/advisories/GHSA-59h8-w5q6-mfmp[WEB]
- https://github.com/triggerdotdev/trigger.dev/pull/4250[WEB]
- https://github.com/triggerdotdev/trigger.dev/commit/73d966ad226548b5f96fb5b4fc6fa607a3b7b8f8[WEB]
- https://github.com/triggerdotdev/trigger.dev[PACKAGE]
- https://github.com/triggerdotdev/trigger.dev/releases/tag/v4.5.5[WEB]