Trigger.dev supervisor: Missing authentication in workload API

Summary

The supervisor workload API of Trigger.dev through version 4.7.6 accepts run-lifecycle requests without authenticating the caller or checking that the run belongs to the caller's deployment. An attacker with network access to the API and a valid run/snapshot pair can start, complete or suspend other runs, and obtain their resolved environment variables and run JWTs. No user interaction is required, but exploitation is considered complex.

Affected

• Trigger.dev (npm package trigger.dev and Docker image ghcr.io/triggerdotdev/trigger.dev) through 4.7.6 (CVE record and VulnCheck)
• Supervisor workload API, port 8020 by default, which is enabled and listens on 0.0.0.0 by default according to the Trigger.dev documentation
• The GitHub advisory lists affected versions as <= 4.6.0, which conflicts with the CVE range; the vendor advisory should be checked

Fixed in

• Unknown. No verified fixed version has been identified.
• The GitHub advisory lists patched versions as >= 4.6.0, which conflicts with the affected range; this must be verified at the vendor advisory.
• Upgrading to 4.7.6 is not confirmed to fix the issue.

Workaround

• No vendor workaround published.
• Do not expose the supervisor workload API port (default 8020) to the internet, user networks or other tenants; restrict it to the components that need it.
• Keep runner containers off networks that also reach the webapp and infrastructure services.

Exploitation

• CISA SSVC: Exploitation none, Automatable no, Technical Impact total.
• Not listed as known exploited (KEV).
• No public proof of concept found; this is not confirmed absent.
• No reports of exploitation in the wild found.

Our recommendation

• Check whether Trigger.dev self-hosted instances are in use and whether the supervisor workload API port is reachable from untrusted networks.
• Restrict access to port 8020 with firewall rules or network segmentation.
• Check the GitHub advisory GHSA-jc26-22qp-cgqj for patched versions and apply the fix as soon as it is confirmed.
• If exposure is suspected, rotate secrets that run environments could have accessed, such as environment variables and credentials.
• Monitor logs for unexpected requests to the workload-actions endpoints.

Public exploits iAttack code is publicly available (PoC on GitHub, Metasploit or Exploit-DB).

PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.

Research sources

• GitHub Security Advisory GHSA-jc26-22qp-cgqj github.com
• VulnCheck Advisory: Trigger.dev through 4.7.6 Missing Authentication in Supervisor Workload API www.vulncheck.com
• OpenCVE: CVE-2026-114085 app.opencve.io
• Strix: CVE-2026-114085 www.strix.ai
• Trigger.dev Changelog v4.7.6 trigger.dev
• Trigger.dev Docs: Supervisor environment variables trigger.dev

Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 31 Oct 2026, 11:17.