# Apache Log4j 2 vulnerability CVE-2021-44228

**URL:** <https://community.jenkins.io/t/apache-log4j-2-vulnerability-cve-2021-44228/990>\
**Category:** Blog & News\
**Created:** [December 10, 2021, 10:53pm UTC](https://community.jenkins.io/t/apache-log4j-2-vulnerability-cve-2021-44228/990 "2021-12-10T22:53:02Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [January 22, 2022, 12:02am UTC](https://community.jenkins.io/t/apache-log4j-2-vulnerability-cve-2021-44228/990/14 "2022-01-22T00:02:10Z")

</div>

> [@gkunkel](#):
>
> How should this be resolved?

As was stated in the other thread. Jenkins doesn’t use log4j, so its not vulnerable to log4j exploits. The blog post your replying to lists ways to test if your install has it. To remedy things, uninstall any plugins that are using it. Or update and hope said plugins got fixed.

---

_[View the full topic](https://community.jenkins.io/t/apache-log4j-2-vulnerability-cve-2021-44228/990)._