# SonarQube, SonarCloud, and the Log4J vulnerability

**URL:** <https://community.sonarsource.com/t/sonarqube-sonarcloud-and-the-log4j-vulnerability/54721>\
**Category:** Sonar Updates\
**Created:** [December 10, 2021, 5:30pm UTC](https://community.sonarsource.com/t/sonarqube-sonarcloud-and-the-log4j-vulnerability/54721 "2021-12-10T17:30:32Z")\
**Posts on this page:** 1\
**Showing post:** 124

<div class="post-metadata">

**Author:** ![Chris](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/chris/32/71589_2.png) [@Chris](https://community.sonarsource.com/u/Chris)\
**Post date:** [December 22, 2021, 5:45pm UTC](https://community.sonarsource.com/t/sonarqube-sonarcloud-and-the-log4j-vulnerability/54721/124 "2021-12-22T17:45:42Z")

</div>

A post was split to a new topic: [SonarQube doesn’t start with an error message about Eleasticsearch](https://community.sonarsource.com/t/sonarqube-doesnt-start-with-an-error-message-about-eleasticsearch/55465)

---

_[View the full topic](https://community.sonarsource.com/t/sonarqube-sonarcloud-and-the-log4j-vulnerability/54721)._