How severe is CVE-2023-46749?

CVE-2023-46749 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-46749?

CVE-2023-46749 affects the following packages: org.apache.shiro:shiro-core (Maven), org.apache.shiro:shiro-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-46749?

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

How do I detect CVE-2023-46749 in my Maven dependencies?

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

How do I mitigate CVE-2023-46749 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-2023-46749 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-46749 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-46749?

CVE-2023-46749 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-46749?

CVE-2023-46749 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-2023-46749 published, and has it been updated?

CVE-2023-46749 was published on January 15, 2024 and was last updated on October 28, 2026. 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

MEDIUM severity

CVE-2023-46749 — shiro-core

MEDIUM

CVE-2023-46749 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in org.apache.shiro:shiro-core. A fix is available for org.apache.shiro:shiro-core — see the affected versions and patch details below.

Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting

Also known asGHSA-jc7h-c423-mpjc

Published

Jan 15, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-46749.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.apache.shiro:shiro-core☕org.apache.shiro:shiro-core

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.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting

Mitigation: Update to Apache Shiro 1.13.0+ or 2.0.0-alpha-4+, or ensure blockSemicolon is enabled (this is the default).

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.shiro:shiro-core`	all versions	1.13.0`org.apache.shiro:shiro-core:1.13.0`
☕Maven	`org.apache.shiro:shiro-core`	≥ 2.0.0alpha1&&< 2.0.0-alpha4	2.0.0-alpha4`org.apache.shiro:shiro-core:2.0.0-alpha4`

Affected Products

1 product · 4 configurations

Application

shiroapache

< 1.13.0

1 version

2.0.0

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.shiro:shiro-core to 1.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46749 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

This flaw can be mitigated by making sure 'blockSemicolon' is enabled.

Source: Red Hat security advisory for CVE-2023-46749 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Fuse 7.13.0	`shiro`	RHSA-2024:3354

Frequently Asked Questions

Apache Shiro before 1.13.0 or 2.0.0-alpha-4, may be susceptible to a path traversal attack that results in an authentication bypass when used together with path rewriting Mitigation: Update to Apache Shiro 1.13.0+ or 2.0.0-alpha-4+, or ensure `blockSemicolon` is enabled (this is the default).

O3 Security · Impact-Aware SCA

Is CVE-2023-46749 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-22Path Traversal

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jan 15, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2023-46749

GHSA-jc7h-c423-mpjc

References

Advisorygithub.com · CVE 2023 46749.json Advisorylists.apache.org · mdv7ftz7k4488rzloxo2fb0p9shnp9wm Advisorynvd.nist.gov · CVE 2023 46749 Advisorysecurity.netapp.com · ntap 20241108 0002 Websecurity.netapp.com · ntap 20241108 0002

Related vulnerabilities

This CVE is medium severity; 6 of 8 other CVEs affecting shiro-core are rated as high or higher (top: critical).

CVE-2026-56130CVE-2026-49268CVE-2026-43827CVE-2026-23901CVE-2022-40664CVE-2022-32532CVE-2016-4437CVE-2021-41303

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2023-46749 — shiro-core

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2023-46749 in your dependencies?