Is CVE-2026-114088 exploited in the wild?

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

How severe is CVE-2026-114088?

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

How is CVE-2026-114088 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-114088?

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-114088: Trigger.dev hardcoded default secret authentication bypass in Socket.IO

CVE-2026-114088 · Severity: medium · CVSS 6.5 · Published 2026-10-21

Trigger.dev is a task orchestration and execution platform used by developers to manage workflow runs and background jobs. In self-hosted deployments before version 4.5.4, an attacker can use a hardcoded default credential baked into the source code to connect to the /coordinator Socket.IO namespace without authentication. This allows the attacker to retrieve decrypted environment variables (including database passwords and API keys) from any workflow run, or forge fake task completion events to corrupt arbitrary runs.

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

Quick answers

Is CVE-2026-114088 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-114088 being exploited in the wild.
How severe is CVE-2026-114088?: Medium severity, with a CVSS score of 6.5, published 21 October 2026.
Which products and versions are affected?: Trigger.dev before 4.5.4.
Is there a fix for CVE-2026-114088?: Yes: fixed in 4.5.4. Until then: Self-hosted operators should immediately upgrade to version 4.5.4 or later, which removes the vulnerable V1 execution stack entirely. Until patching is possible, operators can mitigate by restricting network access to the Socket.IO endpoints and ensuring non-default values are set for PROVIDER_SECRET and COORDINATOR_SECRET environment variables if the application allows overrides. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-114088 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-114088?: 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.4

Self-hosted operators should immediately upgrade to version 4.5.4 or later, which removes the vulnerable V1 execution stack entirely. Until patching is possible, operators can mitigate by restricting network access to the Socket.IO endpoints and ensuring non-default values are set for PROVIDER_SECRET and COORDINATOR_SECRET environment variables if the application allows overrides.

Technical details

The vulnerability involves three chained weaknesses: a hardcoded default COORDINATOR_SECRET ("coordinator-secret") in the source code that is neither documented in configuration examples nor environment files (CWE-798), a READY_FOR_EXECUTION Socket.IO handler that returns decrypted environment variables to any authenticated caller including those using the default secret (CWE-200), and write handlers like TASK_RUN_FAILED_TO_RUN that accept attacker-controlled payloads without authorization checks (CWE-862). Self-hosted deployments running Run Engine 1.0 (V1) are fully exposed to all three issues; Run Engine 2.0 (V4) deployments are vulnerable only to the write handlers. The attack requires network access to the self-hosted webapp and knowledge of an internal run ID or attempt-friendly ID.

Affected products

Trigger.dev Trigger.dev before 4.5.4

Timeline

2026-07-20: disclosed
2026-10-21: advisory

References

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