# \#log4shell

**URL:** https://community.thinlinc.com/tag/log4shell/100.md

[Latest](https://community.thinlinc.com/latest.md) · [Categories](https://community.thinlinc.com/categories.md) · [Tags](https://community.thinlinc.com/tags.md)

---

## [Vulnerability to Log4Shell](https://community.thinlinc.com/t/vulnerability-to-log4shell/285)

<div class="topic-metadata">

**Author:** [@LTimmons](https://community.thinlinc.com/u/LTimmons)\
**Replies:** 2\
**Last updated:** [15 December 2021 13:14 UTC](https://community.thinlinc.com/t/vulnerability-to-log4shell/285 "2021-12-15T13:14:12Z")

</div>

Does anyone know if ThinLinc is vulnerable to the new Log4jShell exploit? -leonard

---

## [Log4Shell Vulnerability](https://community.thinlinc.com/t/log4shell-vulnerability/286)

<div class="topic-metadata">

**Author:** [@aaron](https://community.thinlinc.com/u/aaron)\
**Replies:** 0\
**Last updated:** [14 December 2021 22:03 UTC](https://community.thinlinc.com/t/log4shell-vulnerability/286 "2021-12-14T22:03:12Z")

</div>

We have had several queries over the past few days regarding the recently disclosed “Log4Shell” vulnerability (CVE-2021-4104). As ThinLinc does not contain Java at all, the product is unaffected by this vulnerability.