# Regarding log4j vulnerability

**URL:** <https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [December 14, 2021, 6:33am UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749 "2021-12-14T06:33:37Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Vashiru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vashiru/32/99623_2.png) [@Vashiru](https://discuss.elastic.co/u/Vashiru)\
**Post date:** [January 5, 2022, 5:30pm UTC](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749/5 "2022-01-05T17:30:12Z")

</div>

Logstash v2.17.1 is mitigate against CVE-2021-44832 from the 28th of December. I've asked about it here: [Log4j CVE-2021-44832 (released 28th dec) - is ES vulnerable?](https://discuss.elastic.co/t/log4j-cve-2021-44832-released-28th-dec-is-es-vulnerable/293076) but thus far no conclusive answer.

I don't know about Logstash, but I do know no update containing log4j 2.17.1 has been released yet for Elasticsearch (it would be released in 7.16.3, but the latest as of writing is 7.16.2).

---

_[View the full topic](https://discuss.elastic.co/t/regarding-log4j-vulnerability/291749)._