Is CVE-2026-114086 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-114086 being exploited in the wild.

How severe is CVE-2026-114086?

Medium severity, with a CVSS score of 5.3, published 21 October 2026.

Is there a fix for CVE-2026-114086?

Yes: fixed in 4.5.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-114086 attacked?

It is attacked over the network.

Am I affected by CVE-2026-114086?

Check whether you run 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.

CVE-2026-114086: Trigger.dev missing authentication in realtime streams POST handler

CVE-2026-114086 · Severity: medium · CVSS 5.3 · Published 2026-10-21

Trigger.dev is a platform for orchestrating background jobs and automating workflows. An unauthenticated attacker can inject malicious data into real-time job streams by guessing predictable job identifiers, potentially corrupting job output and affecting production environments. This allows arbitrary data injection without requiring any credentials or authentication.

Technologies: Trigger.dev. Vendors: Trigger.dev.

Quick answers

Is CVE-2026-114086 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114086 being exploited in the wild.
How severe is CVE-2026-114086?: Medium severity, with a CVSS score of 5.3, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.5.
Is there a fix for CVE-2026-114086?: Yes: fixed in 4.5.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114086 attacked?: It is attacked over the network.
Am I affected by CVE-2026-114086?: Check whether you run 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 /realtime/v1/streams/:runId/:streamId POST handler lacks authentication despite handling sensitive real-time data injection. The vulnerability exploits predictable run friendlyIds (e.g., run_1234abcd) and the absence of environment scoping in the run lookup, allowing cross-environment access including production. An attacker can send unauthenticated POST requests with arbitrary JSON payloads to inject data into any run's stream.

Affected products

Trigger.dev Trigger.dev before 4.5.5

Timeline

2026-07-21: disclosed
2026-07-21: patched: Fixed in version 4.5.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.