Summary
Remote code injection in Log4j (through pax-logging-log4j2)
Workarounds
Set system property -Dlog4j2.formatMsgNoLookups=true
References
Impact
Remote Code Execution.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is GHSA-XXFH-X98P-J8FR? GHSA-XXFH-X98P-J8FR is a critical-severity security vulnerability in org.ops4j.pax.logging:pax-logging-log4j2 (maven), affecting versions >= 2.0.0, < 2.0.11. It is fixed in 2.0.11, 1.11.10.
- Which versions of org.ops4j.pax.logging:pax-logging-log4j2 are affected by GHSA-XXFH-X98P-J8FR? org.ops4j.pax.logging:pax-logging-log4j2 (maven) versions >= 2.0.0, < 2.0.11 is affected.
- Is there a fix for GHSA-XXFH-X98P-J8FR? Yes. GHSA-XXFH-X98P-J8FR is fixed in 2.0.11, 1.11.10. Upgrade to this version or later.
- Is GHSA-XXFH-X98P-J8FR exploitable, and should I be worried? Whether GHSA-XXFH-X98P-J8FR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-XXFH-X98P-J8FR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-XXFH-X98P-J8FR?
- Upgrade
org.ops4j.pax.logging:pax-logging-log4j2to 2.0.11 or later - Upgrade
org.ops4j.pax.logging:pax-logging-log4j2to 1.11.10 or later
- Upgrade