This was always going to be an issue when we posted about it last week – here is more information. Log4j 2.15.0 and previously suggested mitigations may not be enough – SANS