Zapier: Security updates in progress for third-party software components
Timeline of updates
- investigatingEdited
We're applying security updates to the Node.js runtime used by parts of Zapier, following a security release from the Node.js project. We have not identified any customer impact or evidence of exploitation, and no action is needed on your part.
Some updates are rolling out now, so you may see brief latency to workflows while they complete.
- investigating
We’re continuing to roll out the security updates and are monitoring the deployment closely. We have not identified any customer impact or evidence of exploitation.
You may continue to see brief workflow latency while updates complete.
We'll continue to keep you up to date as we make progress
- identified
We've made good progress rolling out the security updates and are continuing to work through the remaining components while monitoring closely. We have not identified any customer impact or evidence of exploitation.
We'll continue to keep you up to date as we make progress.
- resolved
We have not identified any customer impact or evidence of exploitation. We have completed the priority security updates and mitigations, and are closing this incident. Remaining lower-risk updates, including updates managed by our providers, will continue as follow-up work.
No action is needed on your part.
Changes Rewindex caught on this incident
- Incident silently edited: Security updates in progress for third-party software components
- Incident updated: Security updates in progress for third-party software components
- Incident updated: Security updates in progress for third-party software components
- Incident updated: Security updates in progress for third-party software components
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 these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
96329bc1913b9ef6…Version 2 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
13ac7ecdc9147908…Version 3 captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
ed4ba007143b61f5…Version 4 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8856cb1da4beb3ad…Version 5 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
3121b62bda41d9dd…
Impact, status and times are the vendor’s own, as last archived. View on status.zapier.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Zapier, started 2026-10-22 15:29 UTC, resolved after 5 d, 4 update(s); edited after publishing.
- Title
- Security updates in progress for third-party software components
- Vendor
- Zapier
- Date
- URL
- https://rewindex.com/company/zapier/incidents/01M5J3NSJ2BYAG62SKG4SC24EH
Zapier profileRecent Zapier incidentsAll outages on October 22, 2026Zapier in October 2026MarkdownJSON