Greenhouse: Mailgun Security Incident
Timeline of updates
- resolved
We are aware of a security incident involving Mailgun, the provider we use for email handling in Greenhouse Recruiting. As a precaution, we have since followed Mailgun's directive to rotate credentials, including the API key and password that Greenhouse uses to send messages through their platform. We have also received assurances after their initial forensics investigation that there does not appear to be any Greenhouse-related data that was accessed through Mailgun. We will continue to engage with Mailgun and the outside party they are working with to analyze the situation and will post additional updates should there be any change in that regard.
From Greenhouse’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.greenhouse.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Greenhouse, started 2018-01-08 19:36 UTC, resolved after 0 min, 1 update(s).
- Title
- Mailgun Security Incident
- Vendor
- Greenhouse
- Date
- URL
- https://rewindex.com/company/greenhouse/incidents/7tgmxqwbwc7f
Greenhouse profileRecent Greenhouse incidentsAll outages on January 8, 2018Greenhouse in January 2018MarkdownJSON