GHSA-59H8-W5Q6-MFMP

GHSA-59H8-W5Q6-MFMP is a medium-severity missing authentication for critical function vulnerability in trigger.dev (npm), affecting versions <= 4.5.4. It is fixed in 4.5.5.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Trigger.dev: Unauthenticated Realtime Stream Data Injection via Run FriendlyId

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

# 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).

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

GHSA-59H8-W5Q6-MFMP has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.5.5); upgrading removes the vulnerable code path.

Affected versions

trigger.dev (<= 4.5.4)

Security releases

trigger.dev → 4.5.5 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade trigger.dev to 4.5.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-59H8-W5Q6-MFMP? GHSA-59H8-W5Q6-MFMP is a medium-severity missing authentication for critical function vulnerability in trigger.dev (npm), affecting versions <= 4.5.4. It is fixed in 4.5.5. A critical operation is accessible without requiring any authentication.
  2. How severe is GHSA-59H8-W5Q6-MFMP? GHSA-59H8-W5Q6-MFMP has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of trigger.dev are affected by GHSA-59H8-W5Q6-MFMP? trigger.dev (npm) versions <= 4.5.4 is affected.
  4. Is there a fix for GHSA-59H8-W5Q6-MFMP? Yes. GHSA-59H8-W5Q6-MFMP is fixed in 4.5.5. Upgrade to this version or later.
  5. Is GHSA-59H8-W5Q6-MFMP exploitable, and should I be worried? Whether GHSA-59H8-W5Q6-MFMP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-59H8-W5Q6-MFMP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-59H8-W5Q6-MFMP? Upgrade trigger.dev to 4.5.5 or later.

Other vulnerabilities in trigger.dev

Stop the waste.
Protect your environment with Kodem.