CLSA-2026-1794208158: TuxCare security update for org.apache.logging.log4j (1 CVE)
Published Nov 9, 2026
·Updated
TuxCare rebuilt 2 org.apache.logging.log4j packages to address 1 CVE. Fixed in 2.6.2-tuxcare.2.
Affected Software
2 affected componentsFixes available
tuxcare/org.apache.logging.log4j:log4j>=2.6.2<2.6.2-tuxcare.2
2.6.2-tuxcare.2
tuxcare/org.apache.logging.log4j:log4j-core>=2.6.2<2.6.2-tuxcare.2
2.6.2-tuxcare.2
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tuxcare/org.apache.logging.log4j:log4jto a version that resolves this vulnerability.Fixed in 2.6.2-tuxcare.2 - Upgrade
Upgrade
tuxcare/org.apache.logging.log4j:log4j-coreto a version that resolves this vulnerability.Fixed in 2.6.2-tuxcare.2 - Upgrade
Upgrade
org.apache.logging.log4jto a version that resolves this vulnerability.Fixed in 2.6.2-tuxcare.2
Event History
Nov 9, 2026
Advisory Published
via OSV·08:09 AM
Data Sourced
via OSV·08:09 AM
DescriptionAffected Software
Frequently Asked Questions
1
Which packages need to be updated?
The update applies to the tuxcare/org.apache.logging.log4j:log4j and tuxcare/org.apache.logging.log4j:log4j-core packages.
2
What fixed version should be deployed?
Deploy version 2.6.2-tuxcare.2 of the affected TuxCare org.apache.logging.log4j packages.