Advisory record · GHSA-xxfh-x98p-j8fr

Remote code injection in Log4j (through pax-logging-log4j2)

No CVSS score

Published by the GitHub Advisory Database at 10 Dec 2021, 20:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.ops4j.pax.logging:pax-logging-log4j2Maven>=2.0.0, <2.0.11 || <1.11.102.0.11, 1.11.10
Identifiers
GHSA-xxfh-x98p-j8fr
Published
10 Dec 2021
Updated
2 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Remote code injection in pax-logging-log4j2 affects versions from 2.0.0 before 2.0.11 and versions before 1.11.10. The source gives few details on the attack conditions, but describes the impact as remote code execution. Upgrade to 1.11.10 or 2.0.11, depending on your release line. If you cannot upgrade, set the system property log4j2.formatMsgNoLookups to true.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.