# Log4Shell comprehensive fix for Elastic Search

**URL:** https://discuss.elastic.co/t/log4shell-comprehensive-fix-for-elastic-search/292106
**Category:** Elasticsearch
**Created:** [December 16, 2021, 8:13am UTC](https://discuss.elastic.co/t/log4shell-comprehensive-fix-for-elastic-search/292106 "2021-12-16T08:13:31Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![rencytl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rencytl/32/99102_2.png) [@rencytl](https://discuss.elastic.co/u/rencytl)
#### Post date: [December 16, 2021, 8:13am UTC](https://discuss.elastic.co/t/log4shell-comprehensive-fix-for-elastic-search/292106/1 "2021-12-16T08:13:31Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 20, 2021, 12:06am UTC](https://discuss.elastic.co/t/log4shell-comprehensive-fix-for-elastic-search/292106/2 "2021-12-20T00:06:38Z")

</div>

Yes we are. It will be **very** soon, but we don't generally provide ETAs sorry.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 17, 2022, 12:07am UTC](https://discuss.elastic.co/t/log4shell-comprehensive-fix-for-elastic-search/292106/3 "2022-01-17T00:07:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
