Is org.ops4j.pax.logging:pax-logging-log4j2 1.8 vulnerable?
Maven · 8 releases from 1.8.0 to 1.8.7 · latest org.ops4j.pax.logging:pax-logging-log4j2 is 2.3.5 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. org.ops4j.pax.logging:pax-logging-log4j2 1.8.7, the last 1.8 release, is affected by 5 known security advisories (3 critical, 1 high, 1 medium), including CVE-2021-45046, CVE-2021-44228, CVE-2021-45105. Upgrade to 1.11.10 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=1.11.10 -DforceVersion=trueIs your project on an affected org.ops4j.pax.logging:pax-logging-log4j2?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.ops4j.pax.logging:pax-logging-log4j2 1.8.7
Improper Input Validation and Injection in Apache Log4j2
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.9 · >=1.11.0 <1.11.13 · >=2.0.0 <2.0.14
- Fixed in
- 1.9.2, 1.10.9, 1.11.13, 2.0.14
Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.9 · >=1.11.0 <1.11.12 · >=2.0.0 <2.0.13
- Fixed in
- 1.9.2, 1.10.9, 1.11.12, 2.0.13
Incomplete fix for Apache Log4j vulnerability
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.8 · >=1.11.0 <1.11.11 · >=2.0.0 <2.0.12
- Fixed in
- 1.9.2, 1.10.8, 1.11.11, 2.0.12
Remote code injection in Log4j (through pax-logging-log4j2)
- Affected
- >=2.0.0 <2.0.11 · <1.11.10
- Fixed in
- 1.11.10, 2.0.11
Remote code injection in Log4j
- Affected
- >=1.8.0 <1.9.2 · >=1.10.0 <1.10.8 · >=1.11.0 <1.11.10 · >=2.0.0 <2.0.11
- Fixed in
- 1.9.2, 1.10.8, 1.11.10, 2.0.11
Every org.ops4j.pax.logging:pax-logging-log4j2 1.8.x release
Affected: 1.8.0 to 1.8.7. Latest org.ops4j.pax.logging:pax-logging-log4j2: 2.3.5.
| Version | Known advisories |
|---|---|
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.7 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.6 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.5 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.4 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.3 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.2 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.1 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
| org.ops4j.pax.logging:pax-logging-log4j2 1.8.0 | CVE-2021-44832, CVE-2021-45105, CVE-2021-45046, GHSA-xxfh-x98p-j8fr, CVE-2021-44228 |
Which of your client projects are still on org.ops4j.pax.logging:pax-logging-log4j2 1.8?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.ops4j.pax.logging:pax-logging-log4j2 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.ops4j.pax.logging:pax-logging-log4j2 versions
- org.ops4j.pax.logging:pax-logging-log4j2 1.11
- org.ops4j.pax.logging:pax-logging-log4j2 1.10
- org.ops4j.pax.logging:pax-logging-log4j2 1.9
- org.ops4j.pax.logging:pax-logging-log4j2 2.3
- org.ops4j.pax.logging:pax-logging-log4j2 2.2
- org.ops4j.pax.logging:pax-logging-log4j2 2.1
- org.ops4j.pax.logging:pax-logging-log4j2 2.0
- org.ops4j.pax.logging:pax-logging-log4j2 1.12
- All org.ops4j.pax.logging:pax-logging-log4j2 advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.