A quick update on the situation now that a new log4j CVE has been created and patched in 2.16.0. We've done research and these are our findings.