We are running Elasticsearch 7.6.2 and have mitigated the log4j by setting the -Dlog4j2.formatMsgNoLookups=true in JVM options.
However, our scans are still showing that Elasticsearch-sql-cli-7.6.2.jar file is vulnerable as it is internally using log4j.
Can let us know if this file can be removed from bin folder or is there a way to mitigate this embedded log4j vulnerability.