# Is it possible to upgrade log4j from 2.11.1 to latest non-vul-ner-able version?

**URL:** https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602
**Category:** Elasticsearch
**Created:** [May 21, 2021, 4:02am UTC](https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602 "2021-05-21T04:02:02Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Elango\_P](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elango_p/32/74447_2.png) [@Elango\_P](https://discuss.elastic.co/u/Elango_P)
#### Post date: [May 21, 2021, 4:02am UTC](https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602/1 "2021-05-21T04:02:02Z")

</div>

Found that ES internally using log4j 2.11.1 which is hitting this [NVD - CVE-2020-9488](https://nvd.nist.gov/vuln/detail/CVE-2020-9488).  
As we are more concerned about security issues, is there any plan to upgrade this in ES v6.8.x or latest versions of ES ? Or manually is it possible to upgrade this jar ?

---

<div class="post-metadata">

### Author: ![Elango\_P](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/elango_p/32/74447_2.png) [@Elango\_P](https://discuss.elastic.co/u/Elango_P)
#### Post date: [May 21, 2021, 10:52am UTC](https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602/2 "2021-05-21T10:52:08Z")

</div>

any updates on this ?

---

<div class="post-metadata">

### Author: ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)
#### Post date: [May 21, 2021, 1:03pm UTC](https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602/3 "2021-05-21T13:03:12Z")

</div>

Please report security issues to [security@elastic.co](mailto:security@elastic.co) as per [the online instructions](https://www.elastic.co/community/security).

Manually upgrading a single JAR is not supported. Since the vulnerability you link apparently affects only some logging configurations, you can likely mitigate it by adjusting your configuration to avoid the vulnerable feature. I believe the default logging configuration is unaffected by this issue.

---

<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: [June 18, 2021, 1:03pm UTC](https://discuss.elastic.co/t/is-it-possible-to-upgrade-log4j-from-2-11-1-to-latest-non-vul-ner-able-version/273602/4 "2021-06-18T13:03:53Z")

</div>

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