Appreciate the efforts having Log4Shell mitigated in versions 7.16.1 and 6.8.21. Is the team working towards providing a comprehensive fix for this upgrading the Log4j library to 2.16.0 version? If yes, knowing the ETA will help for sure.
Yes we are. It will be very soon, but we don't generally provide ETAs sorry.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.