What is GHSA-94G7-HPV8-H9QM?

GHSA-94G7-HPV8-H9QM is a critical-severity security vulnerability in com.splunk.logging:splunk-library-javalogging (maven), affecting versions >= 1.7.0, < 1.11.1. It is fixed in 1.11.1, 1.6.2-0-0.

Which versions of com.splunk.logging:splunk-library-javalogging are affected by GHSA-94G7-HPV8-H9QM?

com.splunk.logging:splunk-library-javalogging (maven) versions >= 1.7.0, < 1.11.1 is affected.

Is there a fix for GHSA-94G7-HPV8-H9QM?

Yes. GHSA-94G7-HPV8-H9QM is fixed in 1.11.1, 1.6.2-0-0. Upgrade to this version or later.

Is GHSA-94G7-HPV8-H9QM exploitable, and should I be worried?

Whether GHSA-94G7-HPV8-H9QM 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.

What actually determines whether GHSA-94G7-HPV8-H9QM 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-94G7-HPV8-H9QM?

Upgrade: com.splunk.logging:splunk-library-javalogging to 1.11.1 or later, com.splunk.logging:splunk-library-javalogging to 1.6.2-0-0 or later.

GHSA-94G7-HPV8-H9QM

Q: Which versions of com.splunk.logging:splunk-library-javalogging are affected by GHSA-94G7-HPV8-H9QM?

com.splunk.logging:splunk-library-javalogging (maven) versions >= 1.7.0, < 1.11.1 is affected.

Q: Is there a fix for GHSA-94G7-HPV8-H9QM?

Yes. GHSA-94G7-HPV8-H9QM is fixed in 1.11.1, 1.6.2-0-0. Upgrade to this version or later.

Q: Is GHSA-94G7-HPV8-H9QM exploitable, and should I be worried?

Whether GHSA-94G7-HPV8-H9QM 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.

Q: What actually determines whether GHSA-94G7-HPV8-H9QM 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.

Q: How do I fix GHSA-94G7-HPV8-H9QM?

Upgrade: com.splunk.logging:splunk-library-javalogging to 1.11.1 or later, com.splunk.logging:splunk-library-javalogging to 1.6.2-0-0 or later.

Summary

Remote code injection in Log4j

Workarounds

If upgrading is not possible, then ensure the -Dlog4j2.formatMsgNoLookups=true system property is set on both client- and server-side components.

References

https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

For more information

If you have any questions or comments about this advisory:

Open an issue in https://github.com/splunk/splunk-library-javalogging/issues
Email us at [email protected]

Impact

Logging untrusted or user controlled data with a vulnerable version of Log4J may result in Remote Code Execution (RCE) against your application. This includes untrusted data included in logged errors such as exception traces, authentication failures, and other unexpected vectors of user controlled input.

More Details:
https://github.com/advisories/GHSA-jfh8-c2jp-5v3q

Affected versions

com.splunk.logging:splunk-library-javalogging (>= 1.7.0, < 1.11.1) com.splunk.logging:splunk-library-javalogging (< 1.6.2-0-0)

Security releases

com.splunk.logging:splunk-library-javalogging → 1.11.1 (maven) com.splunk.logging:splunk-library-javalogging → 1.6.2-0-0 (maven)

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 environment New to Kodem? Get a demo →

Remediation advice

Version 1.11.1 of the Splunk Logging for Java library.

There is also a backport to version 1.6.2 released as a patch: 1.6.2-0-0.

Frequently Asked Questions

What is GHSA-94G7-HPV8-H9QM? GHSA-94G7-HPV8-H9QM is a critical-severity security vulnerability in com.splunk.logging:splunk-library-javalogging (maven), affecting versions >= 1.7.0, < 1.11.1. It is fixed in 1.11.1, 1.6.2-0-0.
Which versions of com.splunk.logging:splunk-library-javalogging are affected by GHSA-94G7-HPV8-H9QM? com.splunk.logging:splunk-library-javalogging (maven) versions >= 1.7.0, < 1.11.1 is affected.
Is there a fix for GHSA-94G7-HPV8-H9QM? Yes. GHSA-94G7-HPV8-H9QM is fixed in 1.11.1, 1.6.2-0-0. Upgrade to this version or later.
Is GHSA-94G7-HPV8-H9QM exploitable, and should I be worried? Whether GHSA-94G7-HPV8-H9QM 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-94G7-HPV8-H9QM 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-94G7-HPV8-H9QM?
- Upgrade com.splunk.logging:splunk-library-javalogging to 1.11.1 or later
- Upgrade com.splunk.logging:splunk-library-javalogging to 1.6.2-0-0 or later