Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven
Not in CISA KEV

Remote code injection in Log4jGHSA-94g7-hpv8-h9qm

GHSA-94g7-hpv8-h9qm is a remote code execution vulnerability in com.splunk.logging:splunk-library-javalogging. A fix is available for com.splunk.logging:splunk-library-javalogging — see the affected versions and patch details below.

Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Aug 7, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
☕com.splunk.logging:splunk-library-javalogging☕com.splunk.logging:splunk-library-javalogging

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Patches

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.

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:

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.splunk.logging:splunk-library-javalogging≥ 1.7.0&&< 1.11.11.11.1com.splunk.logging:splunk-library-javalogging:1.11.1
☕Mavencom.splunk.logging:splunk-library-javaloggingall versions1.6.2-0-0com.splunk.logging:splunk-library-javalogging:1.6.2-0-0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.splunk.logging:splunk-library-javalogging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.splunk.logging:splunk-library-javalogging to 1.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-94g7-hpv8-h9qm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 ### Patches 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. ### Workarounds If upgrading is not possible, then ensure the -Dlog4j2.for
O3 Security · Impact-Aware SCA

Is GHSA-94g7-hpv8-h9qm in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Remote code injection in Log4j