SMARTSHEET · Vendor
NO FIX YET
Smartsheet had a performance change and a separate update flood between August 24 and 28, 2026 that caused some formulas and cross-sheet references to calculate wrong or show errors after row insertions or deletions. Smartsheet reports that data was restored by recalculating affected sheets, and the sources describe a reliability incident rather than an attacker gaining access.
first public Aug 25, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that use Smartsheet formulas, cell links or cross-sheet references on sheets edited between August 24 and 28, 2026 may have seen incorrect values. The sources do not list specific account or plan scopes, and state that full data restoration was completed on August 28, 2026.
Not affected if no-cross-sheet-references
Who cares saas, security, smartsheet
Unknown from the sources.
No fix yet, per the sources.
Between August 24 and August 28, 2026, a performance optimization caused certain formulas and cross-sheet references to evaluate incorrectly or produce errors following row insertions or deletions. The root cause was an asynchronous calculation change that performed partial data loads, omitting dependent cells and silently persisting inaccurate formula values. The issue was mitigated on August 27 at 11:25 AM PDT by disabling the optimization flags, with full data restoration completed on August 28 after recalculating approximately all affected known sheets. Preventive measures include enforcing dependency coverage safeguards and adding automated test suites for structural sheet edits.
Another event also caused the same issues. On August 25, 2026 (starting at ~19:43 UTC), an unprecedented update fanout from a single high-connectivity source sheet overwhelmed the backend Grid Service with approximately update attempts in the thousands, leading to database connection spikes and 502 Bad Gateway errors that left destination sheets with stale cell links and cross-sheet references. Engineering mitigated the propagation by blocking the problematic source sheet on August 26, 2026. A comprehensive, two-phase bulk inbound refresh was subsequently executed across affected unique destination sheets starting on August 26 at 19:14 UTC and successfully concluding on August 27, 2026 at 11:07 UTC, restoring live link consistency across active sheets.
We continue to prioritize investments to scale our networking, compute, security, and other infrastructure, and in the technical management processes that enable us to consistently deliver against that commitment. While we cannot promise a future free of any technical challenges, we promise that we will do whatever it takes to ensure that Smartsheet is a partner that can be counted on to deliver. We know that your success—and your continued trust in Smartsheet—depends on it.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.