Apache Camel is NOT using log4j for production

Apache Camel does not directly depend on Log4j 2, so we are not affected by CVE-2021-44228.

If you explicitly added the Log4j 2 dependency to your own applications, make sure to upgrade.

Apache Camel is using log4j for testing itself

Apache Camel does use log4j during testing itself, and therefore you can find that we have been using log4j v2.13.3 release in our latest LTS releases Camel 3.7.6, 3.11.4.

In the camel-dependencies BOM we extract all the 3rd party dependency version that was used for building and testing the release:


In the upcoming LTS releases 3.14.0, 3.11.5, and 3.7.7 we have upgraded to log4j 2.15.0. UPDATE: We upgrade to log4j 2.16.0 in LTS releases 3.14.1, 3.11.5 and 3.7.7.

For future releases then we plan to filter out testing dependencies in the camel-dependencies BOM, meaning that log4j2-version will no longer be included.

3rd party components with transitive dependency on log4j-core

There are two Camel components, camel-nsq and camel-corda which have a dependency on log4j-core by their 3rd party library. Those libraries do not actively use log4j-core, but rely only on log4j-api. Therefore the maintainers of those projects should correct this in their projects.

At Apache Camel we have corrected this by excluding log4j-core and only depend on log4-api for these two components. This change will be in all upcoming LTS releases.

This should not be a security issue as you are only vulnerable if log4j-core is active in use as the logging framework. Having log4j-core on the classpath and using another logging framework such as logback or jboss-logging is not a problem.

What about other Apache Camel projects?

Camel Quarkus and Camel K

Apache Camel Quarkus and Camel K uses Quarkus as the runtime, and Quarkus does not use log4j, and they are therefore not affected, according to the Quarkus team.

Camel Spring Boot

Camel Spring Boot uses Spring Boot as the runtime, and Spring Boot is only affected if you have chosen to use log4j instead of the default logback logger. See more details from the Spring Boot team announcement.

Camel Kafka Connector

Apache Kafka Connectors runs on Apache Kafka and Kafka uses the older log4 v1 which is not affected.

Camel Karaf

Camel Karaf uses Apache Karaf as the runtime, and Apache Karaf is affected. The latest Karaf release 4.3.3 comes with several versions of log4j such as 2.14.1, 2.13.3 and 2.9.1 The Karaf team is aware of this and are working on a new Karaf 4.3.4 release with updated log4j.

Camel JBang

The camel-jbang module is a new developer tool that was first shipped in Camel 3.12. In Camel 3.13.0 then camel-jbang uses log4j 2.13.3 for logging output. This tool cannot be used for production, as camel-jbang is not a regular Camel component - only a developer tool.

In Camel 3.14.0 then camel-jbang comes with updated log4j v2.15.0. However, in Camel 3.15.0 we will switch to another logger system to avoid log4j at all.

What about Apache Camel 2?

Apache Camel 2 is not affected. The camel-core from Camel 2 uses slf4j-api as the logging facade, and log4j is only used during testing Camel itself.