# Trigger.dev unauthenticated data injection in realtime stream API

Source: https://junglewise.ai/threats/trigger-dev-unauthenticated-realtime-stream-data-injection-via-run-b0ac295b  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-02. Updated: 2026-10-02  
License: CC BY 4.0 with a link back

Severity: medium · CVSS 5.3 · Published 2026-10-02

Trigger.dev's realtime stream API endpoint for job runs lacks authentication, allowing anyone with knowledge of a run ID to inject arbitrary data into active streams. This bypasses environment boundaries and could affect production job monitoring, data pipelines, or real-time notifications by corrupting or falsifying stream data.

Technologies: [trigger.dev (npm)](https://junglewise.ai/threats/technologies/npm-trigger-dev), [Trigger.dev](https://junglewise.ai/threats/technologies/trigger-dev). Vendors: [npm](https://junglewise.ai/threats/vendors/npm), [Trigger.dev](https://junglewise.ai/threats/vendors/trigger-dev).

## Quick answers

**Is This vulnerability exploited in the wild?** No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

**How severe is This vulnerability?** Medium severity, with a CVSS score of 5.3, published 2 October 2026.

**Which products and versions are affected?** trigger.dev (npm) <= 4.5.4; Trigger.dev <= 4.5.4.

**Is there a fix for This vulnerability?** Yes: fixed in 4.5.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is This vulnerability attacked?** It is attacked over the network.

**Am I affected?** Check whether you run trigger.dev (npm) or Trigger.dev at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 4.5.5

## Technical details

The POST handler at `/realtime/v1/streams/:runId/:streamId` has no authentication wrapper and performs run lookups by friendlyId alone, without environment scoping. Run friendlyIds follow predictable patterns (e.g., `run_1234abcd`), making enumeration feasible. An attacker can inject arbitrary JSON into any stream without credentials or authorization checks.

## Affected products

- Trigger.dev trigger.dev <= 4.5.4

## Timeline

- 2026-07-21: disclosed
- 2026-10-02: advisory
- 2026-10-02: patched

## References

- [https://api.github.com/users/sfwani](https://api.github.com/users/sfwani)

## Related threats

- [Trigger.dev cross-site request forgery in logout endpoint](https://junglewise.ai/threats/cve-2026-114093-trigger-dev-before-4-5-6-contains-a-cross-site-request-forgery)
- [Trigger.dev missing authentication in task run replay](https://junglewise.ai/threats/cve-2026-114092-trigger-dev-before-4-5-0-performs-no-authentication-or)
- [Trigger.dev cross-tenant authorization bypass in run replay](https://junglewise.ai/threats/cve-2026-114091-trigger-dev-before-4-5-0-looks-up-runs-by-friendlyid-alone-in)
- [Trigger.dev cross-site request forgery in CLI authorization flow](https://junglewise.ai/threats/cve-2026-114089-trigger-dev-before-4-5-2-contains-a-cross-site-request-forgery)
- [Trigger.dev hardcoded default secret authentication bypass in Socket.IO](https://junglewise.ai/threats/cve-2026-114088-trigger-dev-before-4-5-4-contains-a-hardcoded-default-secret)