We have identified the problem.
An invalid configuration option for the affected tenants coupled with a change in the newly released version is causing the issue.
We have fixed the configuration issue and are applying the configuration changes across the affected tenants.