همهٔ گزارش‌ها
متوسط

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

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
<= 4.5.4
نسخهٔ اصلاح‌شده
4.5.5

بهره‌برداری

CVE-2026-114086

احتمال بهره‌برداری در ۳۰ روز آینده: 0.38%

FIRST EPSS · ۱۴۰۵/۰۸/۳۰

شرح آسیب‌پذیری

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

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

پیوندها

گزارش‌دهندگان

  • sfwani
  • dodge1218
  • geo-chen
  • MatiasTilleriasLey