# Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion

Advisory record · `GHSA-p6xc-xr62-6r2g`

- **Identifiers:** `GHSA-p6xc-xr62-6r2g` · `CVE-2021-45105`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-674](https://cwe.mitre.org/data/definitions/674.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md)
- **Published:** 18 Dec 2021
- **Updated:** 9 Jun 2026
- **Reviewed by a person:** No

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

## Critical

Critical, because:

- CVSS score 8.6 (7.0 or more) and EPSS 1.00 (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

- `org.apache.logging.log4j:log4j-core` (Maven): affected `>=2.4.0, <2.12.3 || >=2.13.0, <2.17.0 || <2.3.1`; fixed in `2.12.3`, `2.17.0`, `2.3.1`
- `org.ops4j.pax.logging:pax-logging-log4j2` (Maven): affected `>=1.8.0, <1.9.2 || >=1.10.0, <1.10.9 || >=1.11.0, <1.11.12 || >=2.0.0, <2.0.13`; fixed in `1.9.2`, `1.10.9`, `1.11.12`, `2.0.13`

## Machine-written summary

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

> Apache Log4j2 (log4j-core) versions 2.0-alpha1 through 2.16.0, excluding 2.12.3, are vulnerable, and pax-logging-log4j2 is also listed as affected in some older lines. An attacker who can control Thread Context Map data can cause a denial of service by supplying a crafted string that triggers uncontrolled recursion through self-referential lookups. Upgrade log4j-core to 2.17.0, 2.12.3, or 2.3.1 for the affected lines, and pax-logging-log4j2 to 1.9.2, 1.10.9, 1.11.12, or 2.0.13.

Written 3 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

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

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

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p6xc-xr62-6r2g)

## Sources

- [GitHub Advisory Database: GHSA-p6xc-xr62-6r2g](https://github.com/advisories/GHSA-p6xc-xr62-6r2g)
- [OSV: GHSA-p6xc-xr62-6r2g](https://osv.dev/vulnerability/GHSA-p6xc-xr62-6r2g)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-45105>
- <https://www.zerodayinitiative.com/advisories/ZDI-21-1541>
- <https://www.oracle.com/security-alerts/cpujul2022.html>
- <https://www.oracle.com/security-alerts/cpujan2022.html>
- <https://www.oracle.com/security-alerts/cpuapr2022.html>
- <https://www.kb.cert.org/vuls/id/930724>
- <https://www.debian.org/security/2021/dsa-5024>
- <https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd>
- <https://security.netapp.com/advisory/ntap-20211218-0001>
- <https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd>
- <https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2021-0032>
- <https://logging.apache.org/log4j/2.x/security.html>

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-p6xc-xr62-6r2g>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p6xc-xr62-6r2g/>. Everything for agents: <https://agentprime.io/llms.txt>.
