Advisory record · GHSA-94g7-hpv8-h9qm

Remote code injection in Log4j

No CVSS score

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

PackageEcosystemAffectedFixed in
com.splunk.logging:splunk-library-javaloggingMaven>=1.7.0, <1.11.1 || <1.6.2-0-01.11.1, 1.6.2-0-0
Identifiers
GHSA-94g7-hpv8-h9qm
Published
14 Dec 2021
Updated
7 Aug 2025

Machine-written summary

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

Splunk Logging for Java (splunk-library-javalogging) versions 1.7.0 up to 1.11.1 and earlier 1.6.x releases are affected. If an attacker can get untrusted or user-controlled data into logged messages, such as exception text or authentication failures, a vulnerable Log4j can lead to remote code execution in the application. Upgrade to version 1.11.1, or to 1.6.2-0-0 if you are on the 1.6 line. If upgrading is not possible, set the system property -Dlog4j2.formatMsgNoLookups=true on client and server components.

Written 7 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:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 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.