Consider the following scenario:
The user can mitigate that by first creating a safe with a different set or order of owners, or a different threshold, and then creating the safe they wished to create (the attacker can still keep front-running those txs though).
A way to mitigate that (prevent front running) is to deploy a fork of SafeProxyFactory with access control - allowing only the protocols Factory to create new safes.
