How severe is CVE-2010-3863?

No CVSS score has been assigned to CVE-2010-3863 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-3863?

CVE-2010-3863 affects the following packages: org.apache.shiro:shiro-root (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-3863?

Update org.apache.shiro:shiro-root to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3863 is resolved across your whole dependency graph.

How do I detect CVE-2010-3863 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-root, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2010-3863 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2010-3863 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2010-3863, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2010-3863?

CVE-2010-3863 has an EPSS (Exploit Prediction Scoring System) score of 54.5%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2010-3863?

CVE-2010-3863 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2010-3863 published, and has it been updated?

CVE-2010-3863 was published on May 14, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2010-3863 — shiro-root

CVE-2010-3863 is a Path Traversal vulnerability in org.apache.shiro:shiro-root. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.apache.shiro:shiro-root — see the affected versions and patch details below.

Apache Shiro Path Traversal vulnerability

Published

May 14, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

54.5%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.apache.shiro:shiro-root

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Shiro before 1.1.0, and JSecurity 0.9.x, does not canonicalize URI paths before comparing them to entries in the shiro.ini file, which allows remote attackers to bypass intended access restrictions via a crafted request, as demonstrated by the /./account/index.jsp URI.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.shiro:shiro-root`	all versions	1.1.0`org.apache.shiro:shiro-root:1.1.0`

Affected Products

2 products · 2 configurations

Application

shiroapache

≤ 1.0.0

range

Application

jsecurityjsecurity

1 version

0.9.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-34952remotemultiple✓ Verified

Apache Shiro - Directory Traversal

by Luke Taylor · Nov 2, 2010

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.shiro:shiro-root, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.shiro:shiro-root to 1.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3863 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.