At my company we are doing our due diligence as a java shop and in all the code we have been scouring we have not found anything exploitable.
The configuration in use here is not the most common for modern development practices and spring. This only affects non JSON APIs using the WebDataBinder.
The do not believe the point about tomcat is correct. Testing the most simple payload that directly interacts with the class loader is not triggering because the class loader in non-standalone tomcat does not allow accessing these fields.
In fact tomcat is patching this as well to prevent this from happening. This configuration of Tomcat is part of the problem. I'm open to seeing proof otherwise, but so far there has been nothing published that shows that other servlet configurations are exploitable.