# Apache Shiro vulnerable to path traversal

Advisory record · `GHSA-jc7h-c423-mpjc`

- **Identifiers:** `GHSA-jc7h-c423-mpjc` · `CVE-2023-46749`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 15 Jan 2024
- **Updated:** 4 Nov 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Jan 2024, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.apache.shiro:shiro-core` (Maven): affected `<1.13.0 || >=2.0.0alpha1, <2.0.0-alpha4`; fixed in `1.13.0`, `2.0.0-alpha4`

## Machine-written summary

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

> Apache Shiro (org.apache.shiro:shiro-core) versions before 1.13.0 and from 2.0.0-alpha1 before 2.0.0-alpha4 are affected. A path traversal flaw can lead to an authentication bypass when Shiro is used together with path rewriting, and the source gives few details on the exact conditions. Upgrade to 1.13.0 or 2.0.0-alpha4 or later; if upgrading is not possible, keep the blockSemicolon setting enabled, which is the default.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.012, the 68th percentile, on 14 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-jc7h-c423-mpjc)

## Sources

- [GitHub Advisory Database: GHSA-jc7h-c423-mpjc](https://github.com/advisories/GHSA-jc7h-c423-mpjc)
- [OSV: GHSA-jc7h-c423-mpjc](https://osv.dev/vulnerability/GHSA-jc7h-c423-mpjc)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-46749>
- <https://lists.apache.org/thread/mdv7ftz7k4488rzloxo2fb0p9shnp9wm>
- <https://security.netapp.com/advisory/ntap-20241108-0002>

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-jc7h-c423-mpjc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jc7h-c423-mpjc/>. Everything for agents: <https://agentprime.io/llms.txt>.