# Path Traversal in Apache Shiro

Advisory record · `GHSA-pmhc-2g4f-85cg`

- **Identifiers:** `GHSA-pmhc-2g4f-85cg` · `CVE-2023-34478`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 24 Jul 2023
- **Updated:** 13 Feb 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Jul 2023, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.

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

## Affected packages

- `org.apache.shiro:shiro-web` (Maven): affected `<1.12.0 || >=2.0.0-alpha-1, <2.0.0-alpha-3`; fixed in `1.12.0`, `2.0.0-alpha-3`

## Machine-written summary

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

> Apache Shiro (shiro-web) versions before 1.12.0 and from 2.0.0-alpha-1 up to 2.0.0-alpha-3 are affected. The source describes a path traversal flaw that can lead to an authentication bypass when Shiro is used with APIs or web frameworks that route requests based on non-normalized paths, but it gives few details on the exact attack conditions. Upgrade to shiro-web 1.12.0 or 2.0.0-alpha-3 or later.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.021, the 81st percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pmhc-2g4f-85cg)

## Sources

- [GitHub Advisory Database: GHSA-pmhc-2g4f-85cg](https://github.com/advisories/GHSA-pmhc-2g4f-85cg)
- [OSV: GHSA-pmhc-2g4f-85cg](https://osv.dev/vulnerability/GHSA-pmhc-2g4f-85cg)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-34478>
- <https://github.com/apache/shiro/commit/c3ede3f94efb442acb0795714a022c2c121d1da0>
- <https://github.com/apache/shiro>
- <https://lists.apache.org/thread/mbv26onkgw9o35rldh7vmq11wpv2t2qk>
- <https://security.netapp.com/advisory/ntap-20230915-0005>
- <http://www.openwall.com/lists/oss-security/2023/07/24/4>

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-pmhc-2g4f-85cg>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pmhc-2g4f-85cg/>. Everything for agents: <https://agentprime.io/llms.txt>.
