threatdeck
Live 14:45 UTC ·

AI Stack Alert Medium TD-2026-0042 For CISO, SOC / IR, AppSec, AI Eng Unconfirmed AI-assisted

Trigger.dev incident exposed environment variables for a subset of customers

Trigger.dev, a cloud-hosted AI workflow platform, disclosed a security incident in a report published on Sunday. The company said an attacker gained unauthorized access to environment variables belonging to a subset of organizations, and that the exploit used has been blocked. Affected customers have been notified, but Trigger has not named the affected organizations and has not published details of the exploit.

Why it matters

Environment variables often hold API keys and other credentials. An attacker holding them could reach the customer's connected services, including webhook integrations such as Stripe, Supabase, and Slack.

Do this

  1. Check whether your organization received a notice from Trigger.dev. Treat any project that uses Trigger.dev as in scope until confirmed otherwise.
  2. Rotate all secrets stored as environment variables in affected Trigger.dev projects, starting with credentials for payment, database, and messaging integrations.
  3. Review audit logs for connected services (for example Stripe, Supabase, Slack) for unusual API use since the incident window.
  4. Follow Trigger.dev's guidance to the affected customer and review the full incident report when it is published.
  5. If you self-host Trigger.dev, which is open source, confirm your deployment's environment variables and access controls separately from the hosted service.

Signals

  • NoCISA KEV
  • 24/100Priority
  • 60%Confidence

Evidence

“an attacker had gained unauthorized access to environment variables belonging to those organizations”

The Register: Security

“Trigger has not publicly identified which organizations were affected by the intrusion.”

The Register: Security

“affected customers have been notified of steps they need to take to prevent further security problems”

The Register: Security

Sources

Affected / related

Trigger.dev, Trigger.dev

Published 2026-11-02 16:44 UTC · updated 2026-11-08 17:53 UTC · AI-assisted summary, checked against quoted sources · Unconfirmed: single non-official source · How we score

Following

Follow the vendors, products, AI tools, techniques and actors you care about. Matching stories, CVEs and exploited bugs are marked, a Following tab appears in the feed, and returning visits show what changed. Saved only in this browser.

Presets

Get updates

A personal RSS feed of new stories on everything you follow. Paste it into any feed reader, Slack or Teams RSS app.