# LOG4J vulenrability

**URL:** <https://discuss.elastic.co/t/log4j-vulenrability/295847>\
**Category:** Elasticsearch\
**Created:** [January 31, 2022, 2:00pm UTC](https://discuss.elastic.co/t/log4j-vulenrability/295847 "2022-01-31T14:00:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [January 31, 2022, 2:06pm UTC](https://discuss.elastic.co/t/log4j-vulenrability/295847/2 "2022-01-31T14:06:30Z")

</div>

There's [this blog post](https://www.elastic.co/blog/log4j2-vulnerability-what-to-know-security-vulnerability-learn-more-elastic-support) and [this announcement](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476). They should be readily available on all major search engines - for instance here on [Google](https://www.google.com/search?q=elastic+log4j+vulnerability).

---

_[View the full topic](https://discuss.elastic.co/t/log4j-vulenrability/295847)._