Remote code injection in Log4j (through pax-logging-log4j2)
Impact
Remote Code Execution.
Patches
Users of pax-logging 1.11.9 should update to 1.11.10. Users of pax-logging 2.0.10 should update to 2.0.11.
Workarounds
Set system property -Dlog4j2.formatMsgNoLookups=true
References
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.ops4j.pax.logging:pax-logging-log4j2 | >= 2.0.0, < 2.0.11, < 1.11.10 | 2.0.11, 1.11.10 |
References
- Weakness (CWE)
-- Platform
- Java / Kotlin (Maven)
- Package
org.ops4j.pax.logging:pax-logging-log4j2- Disclosed
- 10.12.2021
- Updated
- 11.10.2026 12:21
Sources and licenses
OSV / GitHub Advisory Database - GHSA-xxfh-x98p-j8fr - CC BY 4.0
Vulnerability history: org.ops4j.pax.logging:pax-logging-log4j2
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 5
- First → latest
- 12.2021 01.2022
- Without a fix
- 0
- Exploited in attacks
- 2
Severity breakdown
- Critical 3
- High 1
- Medium 1
Disclosures per year
- 2021: 4
- 2022: 1
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 0
-
Remote code injection in Log4j (through pax-logging-log4j2) this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.