We identified this as an issue 2 weeks ago, so we were well ahead of the curve in taking corrective measures.
Big thanks to @TNE for rolling out the hotfix so quickly.