# Security Disclosure: Sunday November 1st

- Provider: [Trigger.dev](https://down.guide/providers/trigger-dev)
- Confidence: Confirmed
- Impact: Degraded
- lasted 4d 13h
- started 2026-11-01 22:50 UTC
- API
- id: DWN-c704a53289
- Official page: https://status.trigger.dev/incidents/1110434

## Updates from Trigger.dev
### 2026-11-01 22:50 UTC: 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.

### 2026-11-06 12:27 UTC: resolved
We’ve published our report on the November 1, 2026 security incident: \[https://trigger.dev/blog/security-incident-report-nov-2026\](https://trigger.dev/blog/security-incident-report-nov-2026)

From the builder: does your app depend on Trigger.dev? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=trigger-dev) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Trigger.dev.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-c704a53289), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.