CLSA-2026-1793354113: TuxCare security update for org.apache.logging.log4j (5 CVEs)

Published Oct 30, 2026
·
Updated

TuxCare rebuilt 19 org.apache.logging.log4j packages to address 5 CVEs. Fixed in 2.25.2-tuxcare.1.

Affected Software

19 affected componentsFixes available
tuxcare/org.apache.logging.log4j:log4j-1.2-api>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-cassandra>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-core>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-core-test>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-couchdb>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-docker>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-jakarta-jms>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-jakarta-smtp>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-jakarta-web>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-jdbc-dbcp2>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-jpa>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-layout-template-json>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-mongodb>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-mongodb4>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-slf4j-impl>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-slf4j2-impl>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-spring-boot>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-spring-cloud-config-client>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1
tuxcare/org.apache.logging.log4j:log4j-web>=2.25.2<2.25.2-tuxcare.1
2.25.2-tuxcare.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  2. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  3. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  4. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  5. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  6. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  7. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  8. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  9. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  10. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  11. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  12. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  13. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  14. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  15. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  16. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  17. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  18. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  19. Upgrade

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

    Fixed in 2.25.2-tuxcare.1
  20. Upgrade

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

    Fixed in 2.25.2-tuxcare.1

Event History

Oct 30, 2026
Advisory Published
via OSV·10:55 AM
Data Sourced
via OSV·10:55 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

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