Trigger.dev
@triggerdotdev
We’ve published our report on the November 1st security incident trigger.dev/blog/security-incident-repor…
Environment variables
Security incidents tagged Environment variables. Newest first.
1 Environment variables incident in the last 12 months
Critical 4 · High 3 · Med 2 · Low 1 · Update ½Severity-weighted: critical 4 · high 3 · medium 2 · low 1 · update ½LessMore
- Incidents
- 1
- Live
- 1
- Patched
- 0
- Days without an incident
- 0
- Longest quiet run: 3 days (Nov 3–Nov 5)
Sponsored
Brought to you byTinkerer Club
The private club for people who own their servers, run their own AI, and pay $0/month for software.
- HighPartly patched
Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers
On Nov 1 2026 Trigger.dev disclosed a security incident: an attacker obtained customer root API keys for some environments and used them to access environment variables. The Nov 6 incident report says 0.66% of customers were impacted, that the attacker listed recent runs/deployments/schedules in some environments, and that there is no evidence of access to other customer data, production databases, or dashboard accounts. Trigger.dev blocked the attacker, mitigated the attack vector, revoked impacted API keys, notified affected customers by email and dashboard banner, engaged IR experts, notified law enforcement, and released IP whitelisting for scoped API keys plus OIDC support. Impacted customers (emails ~21:36 UTC Nov 1 and ~20:27 UTC Nov 2) should regenerate Trigger.dev API keys and rotate credentials in affected environments. Self-hosted deployments were not impacted. The attack vector is still withheld pending the investigation. Status page marked the disclosure Resolved on Nov 6 when the full report published.
Trigger.dev (hosted background jobs / AI workflows)Since Nov 1, 2026
Posts 2
- Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customers
- Trigger.dev: attacker accessed environment variables and root API keys for 0.66% of customersTrigger.dev@triggerdotdev
There has been a security incident at Trigger. We have emailed the owners of all impacted accounts. We’ll be providing more information but for now the focus is on giving the impacted account owners what they need to mitigate. trigger.dev/blog/security-incident-nov-2…
