# Deserialization of Untrusted Data in Log4j 1.x

Advisory record · `GHSA-w9p3-5cr8-m3jj`

- **Identifiers:** `GHSA-w9p3-5cr8-m3jj` · `CVE-2022-23302`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 21 Jan 2022
- **Updated:** 9 Jul 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Jan 2022, 23:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 8.8 (7.0 or more) and EPSS 0.64 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `log4j:log4j` (Maven): affected `<=1.2.17`; no fixed version yet
- `org.zenframework.z8.dependencies.commons:log4j-1.2.17` (Maven): affected `<=2.0`; no fixed version yet

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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.64, the 99th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## 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-w9p3-5cr8-m3jj)

## Sources

- [GitHub Advisory Database: GHSA-w9p3-5cr8-m3jj](https://github.com/advisories/GHSA-w9p3-5cr8-m3jj)
- [OSV: GHSA-w9p3-5cr8-m3jj](https://osv.dev/vulnerability/GHSA-w9p3-5cr8-m3jj)
- <https://nvd.nist.gov/vuln/detail/CVE-2022-23302>
- <https://github.com/apache/logging-log4j1>
- <https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w>
- <https://logging.apache.org/log4j/1.2/index.html>
- <https://security.netapp.com/advisory/ntap-20220217-0006>
- <https://www.oracle.com/security-alerts/cpuapr2022.html>
- <https://www.oracle.com/security-alerts/cpujul2022.html>
- <https://www.vicarius.io/vsociety/posts/cve-2022-23302-detect-log4j-1217-vulnerability>
- <https://www.vicarius.io/vsociety/posts/cve-2022-23302-mitigate-log4j-1217-vulnerability>
- <http://www.openwall.com/lists/oss-security/2022/01/18/3>

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-w9p3-5cr8-m3jj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-w9p3-5cr8-m3jj/>. Everything for agents: <https://agentprime.io/llms.txt>.
