# Remote code injection in Log4j

Advisory record · `GHSA-94g7-hpv8-h9qm`

- **Identifiers:** `GHSA-94g7-hpv8-h9qm`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **Published:** 14 Dec 2021
- **Updated:** 7 Aug 2025
- **Reviewed by a person:** No

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.

## Affected packages

- `com.splunk.logging:splunk-library-javalogging` (Maven): affected `>=1.7.0, <1.11.1 || <1.6.2-0-0`; fixed in `1.11.1`, `1.6.2-0-0`

## 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

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-94g7-hpv8-h9qm)

## Sources

- [GitHub Advisory Database: GHSA-94g7-hpv8-h9qm](https://github.com/advisories/GHSA-94g7-hpv8-h9qm)
- [OSV: GHSA-94g7-hpv8-h9qm](https://osv.dev/vulnerability/GHSA-94g7-hpv8-h9qm)
- <https://github.com/splunk/splunk-library-javalogging/security/advisories/GHSA-94g7-hpv8-h9qm>
- <https://github.com/splunk/splunk-library-javalogging>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-94g7-hpv8-h9qm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-94g7-hpv8-h9qm/>. Everything for agents: <https://agentprime.io/llms.txt>.
