CLSA-2026-1793724931: TuxCare security update for org.apache.logging.log4j (1 CVE)
Published Nov 3, 2026
·Updated
TuxCare rebuilt 2 org.apache.logging.log4j packages to address 1 CVE. Fixed in 2.7-tuxcare.2.
Affected Software
2 affected componentsFixes available
tuxcare/org.apache.logging.log4j:log4j-1.2-api>=2.7<2.7-tuxcare.2
2.7-tuxcare.2
tuxcare/org.apache.logging.log4j:log4j-core>=2.7<2.7-tuxcare.2
2.7-tuxcare.2
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
tuxcare/org.apache.logging.log4j:log4j-1.2-apito a version that resolves this vulnerability.Fixed in 2.7-tuxcare.2 - Upgrade
Upgrade
tuxcare/org.apache.logging.log4j:log4j-coreto a version that resolves this vulnerability.Fixed in 2.7-tuxcare.2 - Upgrade
Upgrade
org.apache.logging.log4jto a version that resolves this vulnerability.Fixed in 2.7-tuxcare.2
Event History
Nov 3, 2026
Advisory Published
via OSV·05:55 PM
Data Sourced
via OSV·05:55 PM
DescriptionAffected Software
Frequently Asked Questions
1
Which packages need to be updated?
The update applies to the TuxCare org.apache.logging.log4j packages log4j-1.2-api and log4j-core.
2
What version contains the fix?
The listed CVE is fixed in version 2.7-tuxcare.2.