CLSA-2026-1793191907: TuxCare security update for org.apache.logging.log4j (1 CVE)

Published Oct 28, 2026
ยท
Updated

TuxCare rebuilt 30 org.apache.logging.log4j packages to address 1 CVE. Fixed in 2.24.3-tuxcare.5.

Affected Software

30 affected componentsFixes available
tuxcare/org.apache.logging.log4j:log4j>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-1.2-api>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-api>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-api-test>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-appserver>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-bom>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-cassandra>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-core>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-core-test>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-couchdb>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-docker>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-iostreams>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jakarta-smtp>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jakarta-web>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jcl>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jdbc-dbcp2>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jpa>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jpl>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-jul>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-layout-template-json>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-mongodb>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-mongodb4>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-slf4j-impl>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-slf4j2-impl>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-spring-boot>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-spring-cloud-config-client>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-taglib>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-to-jul>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-to-slf4j>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5
tuxcare/org.apache.logging.log4j:log4j-web>=2.24.3<2.24.3-tuxcare.5
2.24.3-tuxcare.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  2. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-1.2-api to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  3. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-api to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  4. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-api-test to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  5. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-appserver to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  6. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-bom to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  7. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-cassandra to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  8. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-core to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  9. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-core-test to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  10. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-couchdb to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  11. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-docker to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  12. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-iostreams to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  13. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jakarta-smtp to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  14. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jakarta-web to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  15. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jcl to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  16. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jdbc-dbcp2 to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  17. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jpa to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  18. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jpl to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  19. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-jul to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  20. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-layout-template-json to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  21. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-mongodb to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  22. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-mongodb4 to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  23. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-slf4j-impl to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  24. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-slf4j2-impl to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  25. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-spring-boot to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  26. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-spring-cloud-config-client to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  27. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-taglib to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  28. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-to-jul to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  29. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-to-slf4j to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  30. Upgrade

    Upgrade tuxcare/org.apache.logging.log4j:log4j-web to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5
  31. Upgrade

    Upgrade org.apache.logging.log4j to a version that resolves this vulnerability.

    Fixed in 2.24.3-tuxcare.5

Event History

Oct 28, 2026
Advisory Published
via OSVยท12:51 PM
Data Sourced
via OSVยท12:51 PM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which components should be prioritized for remediation?

Prioritize systems using the rebuilt org.apache.logging.log4j packages, particularly log4j-core. The advisory also covers log4j, log4j-1.2-api, log4j-api, log4j-api-test, log4j-appserver, log4j-bom, and log4j-cassandra.

2

What package version contains the fix?

The fix is included in version 2.24.3-tuxcare.5.

3

How broad is this update?

TuxCare rebuilt 30 org.apache.logging.log4j packages to address one CVE. The provided advisory does not identify the CVE or describe exploit prerequisites, affected configurations, or temporary mitigations.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
ยฉ 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203