org.ops4j.pax.logging:pax-logging-log4j2 (maven) has 4 known vulnerabilities, the worst rated CRITICAL. Upgrade to 2.0.14 or later to clear all of them. No malicious-package signal is recorded.
0 direct dependencies
none carry a known advisory
0 packages depend on it
dependents not yet indexed for this ecosystem
Tracked for PyPI packages. HuggingFace models declare Python dependencies, so maven packages are not covered.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 100th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-7rjr-3q55-vv33, the advisory selected below
The fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for org.ops4j.pax.logging:pax-logging-log4j2 (maven), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 4 known vulnerabilities for org.ops4j.pax.logging:pax-logging-log4j2 (maven), the worst rated CRITICAL. They are GHSA-7rjr-3q55-vv33, GHSA-xxfh-x98p-j8fr, GHSA-p6xc-xr62-6r2g, GHSA-8489-44mv-ggj8.
2.0.14 or later clears every advisory recorded for org.ops4j.pax.logging:pax-logging-log4j2 (maven). Check the release you pick before installing it.
Search org.ops4j.pax.logging:pax-logging-log4j2 in CyberXYZ Check at https://cyberxyz.io/check?q=org.ops4j.pax.logging%3Apax-logging-log4j2. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:37 UTC. The most recent advisory here was published 2022-01-04. Updated continuously from NVD, GHSA, OSV and CNA feeds.