# Elasticsearch-sql-cli jar and log4j vulnerabilty **URL:** \ **Category:** Elasticsearch\ **Created:** [February 17, 2022, 10:32pm UTC](https://discuss.elastic.co/t/elasticsearch-sql-cli-jar-and-log4j-vulnerabilty/297550 "2022-02-17T22:32:19Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![praveen4bv](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/praveen4bv/32/45595_2.png) [@praveen4bv](https://discuss.elastic.co/u/praveen4bv)\ **Post date:** [February 17, 2022, 10:32pm UTC](https://discuss.elastic.co/t/elasticsearch-sql-cli-jar-and-log4j-vulnerabilty/297550/1 "2022-02-17T22:32:19Z")
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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 17, 2022, 10:32pm UTC](https://discuss.elastic.co/t/elasticsearch-sql-cli-jar-and-log4j-vulnerabilty/297550/2 "2022-02-17T22:32:20Z")
Elasticsearch 7.6 is [EOL](https://www.elastic.co/support/eol) and no longer supported. Please upgrade ASAP. (This is an automated response from your friendly Elastic bot. Please report this post if you have any suggestions or concerns :elasticheart: ) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 17, 2022, 10:33pm UTC](https://discuss.elastic.co/t/elasticsearch-sql-cli-jar-and-log4j-vulnerabilty/297550/3 "2022-03-17T22:33:09Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.