Trigger.dev: Security Disclosure: Sunday November 1st
Affected components: API
Timeline of updates
- resolved
There has been a security incident at Trigger.dev.
We've blocked the exploit used in this attack but our investigation has identified exposure across a subset of organizations.
The attacker gained unauthorized access to environment variables for these organizations.
We have emailed all impacted account owners with steps to mitigate.
We will follow up with more details.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-01 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
aaa1bb19347c58a6…
Impact, status and times are the vendor’s own, as last archived.
Cite this
Status incident (vendor impact label: none) posted by Trigger.dev, started 2026-11-01 22:50 UTC, resolved after 0 min, 1 update(s).
- Title
- Security Disclosure: Sunday November 1st
- Vendor
- Trigger.dev
- Date
- URL
- https://rewindex.com/company/trigger-dev/incidents/1110434
Trigger.dev profileRecent Trigger.dev incidentsAll outages on November 1, 2026Trigger.dev in November 2026MarkdownJSON