PT-2026-111184
Published
2026-10-02
·
Updated
2026-10-02
Description by
CVSS 3.1
5.3
MediumMetricsAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.tsThe
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).
Found an issue in the description? Have something to add? Feel free to write us 👾