# Beats are not vulnerable to Log4j2 RCE
**URL:** https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992
**Category:** Beats
**Created:** [December 15, 2021, 2:19pm UTC](https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992 "2021-12-15T14:19:57Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@dave101](https://discuss.elastic.co/u/dave101)
#### Post date: [December 15, 2021, 2:19pm UTC](https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992/1 "2021-12-15T14:19:57Z")
Hi there, maybe some can confirm the follow for us. A few days ago we read this article concerning the log4j vulnerability.
# [Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228 - ESA-2021-31](https://discuss.elastic.co/t/apache-log4j2-remote-code-execution-rce-vulnerability-cve-2021-44228-esa-2021-31/291476)
Here it is stated that BEATS is not affected by this vulnerability. But just to be sure, cause we are still running on version 7.9.0, don't ask why 😉 is our version safe from the log4j? as we cannot upgrade.
Thank you very much.
Regards,
Dave
---
### Author:  [@legoguy1000](https://discuss.elastic.co/u/legoguy1000)
#### Post date: [December 15, 2021, 2:20pm UTC](https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992/2 "2021-12-15T14:20:45Z")
Beats are written in GoLang not java.
---
### Author:  [@dave101](https://discuss.elastic.co/u/dave101)
#### Post date: [December 15, 2021, 2:27pm UTC](https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992/3 "2021-12-15T14:27:46Z")
Thanks Alex for the very fast reply! Good to hear it's not affected, so we can proceed calmly 🤓
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 12, 2022, 4:28pm UTC](https://discuss.elastic.co/t/beats-are-not-vulnerable-to-log4j2-rce/291992/4 "2022-01-12T16:28:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.