dbcve.org
ShiroApplication · Apache

CVE-2026-23903

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-09
Fix available
A fix is available. Upgrade to 2.0.7 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication Bypass by Alternate Name vulnerability in Apache Shiro. This issue affects Apache Shiro: before 2.0.7. Users are recommended to upgrade to version 2.0.7, which fixes the issue. The issue only effects static files. If static files are served from a case-insensitive filesystem, such as default macOS setup, static files may be accessed by varying the case of the filename in the request. If only lower-case (common default) filters are present in Shiro, they may be bypassed this way. Shiro 2.0.7 and later has a new parameters to remediate this issue shiro.ini: filterChainResolver.caseInsensitive = true application.propertie: shiro.caseInsensitive=true Shiro 3.0.0 and later (upcoming) makes this the default.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authentication bypass vulnerability in Apache Shiro allows accessing static files by varying the case of the filename on case-insensitive filesystems (e.g., macOS). If only lowercase filters are configured, attackers can bypass authentication by using mixed-case URLs that match the filesystem's case-insensitive lookup.

MitigationUpgrade to Apache Shiro 2.0.7 or later and set shiro.caseInsensitive=true (in application.properties) or filterChainResolver.caseInsensitive=true (in shiro.ini) to enforce consistent case handling in filter matching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShiroApplication
Affected:< 2.0.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Shiro version
    Check your project's dependency management (Maven pom.xml, Gradle build.gradle, or the shiro-core JAR META-INF/MANIFEST.MF) to determine the installed Shiro version
    Affected if The version is less than 2.0.7
  2. Determine filesystem case sensitivity
    On macOS, verify the filesystem is case-insensitive by default (APFS default). On Linux, check with 'df -T /' - if the filesystem type is not case-sensitive (unlikely on Linux), note this. This vulnerability primarily affects macOS and Windows filesystems.
    Affected if Running on a case-insensitive filesystem (macOS APFS default, Windows NTFS) AND Shiro version < 2.0.7
  3. Check for caseInsensitive configuration setting
    Search configuration files (application.properties, application.yml, shiro.ini) for 'shiro.caseInsensitive' or 'filterChainResolver.caseInsensitive' settings
    Affected if The setting is absent, set to false, or not present in configuration AND version < 2.0.7 on a case-insensitive filesystem
  4. Inspect filter chain URL patterns
    Review filter chain definitions in shiro.ini or Java configuration for URL patterns - look for filters that only define lowercase paths (e.g., '/admin/** = authc') without corresponding uppercase or mixed-case variants
    Affected if Filter chains use only lowercase URL patterns without explicit case handling AND version < 2.0.7 on a case-insensitive filesystem

A user is affected if running Apache Shiro version < 2.0.7 on a case-insensitive filesystem (macOS default) without the caseInsensitive configuration enabled and with lowercase-only filter chain definitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.7 or later
Fixed in 2.0.7
Interim mitigation

Upgrade to Apache Shiro 2.0.7 or later and set shiro.caseInsensitive=true (in application.properties) or filterChainResolver.caseInsensitive=true (in shiro.ini) to enforce consistent case handling in filter matching.

Recommended fix High confidence

Apache Shiro 2.0.7

  1. 1. Download Apache Shiro version 2.0.7 or later from the official Apache distribution (https://shiro.apache.org/download.html)
  2. 2. Update your project's dependency management to use shiro-core version 2.0.7 or higher (e.g., in pom.xml for Maven or build.gradle for Gradle)
  3. 3. Rebuild your application with the updated dependency
  4. 4. Redeploy the rebuilt application to your environment
  5. 5. Verify that static file access controls are functioning correctly after the upgrade
  6. 6. If upgrade is not immediately feasible, add the configuration shiro.caseInsensitive=true to application.properties OR filterChainResolver.caseInsensitive=true to shiro.ini as a mitigation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shiro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23903 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23903 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data