dbcve.org
CWE-289Weakness · CWE-289

CVE-2026-56091

HIGH · 8.2 CVSS v4.0 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
When using Apache Shiro with the shiro-guice module in a web servlet context, a specially crafted HTTP request may cause an authentication bypass. This vulnerability is similar to https://www.cve.org/CVERecord?id=CVE-2020-1957 https://www.cve.org/CVERecord , except that it affects the `shiro-guice` module instead of the `shiro-spring` module. This issue affects all Apache Shiro versions through 2.x, and 3.0.0-alpha-1 only when using `shiro-guice` module in a web servlet context. Upgrade to version 3.0.0 or later, which fixes the issue.

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

Apache Shiro's shiro-guice module contains an authentication bypass vulnerability when used in a web servlet context. A specially crafted HTTP request can bypass authentication checks, similar to the path traversal issue in CVE-2020-1957 but affecting the guice integration module instead of spring.

MitigationUpgrade Apache Shiro to version 3.0.0 or later when using the shiro-guice module in a web servlet context to resolve this authentication bypass.

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

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
Authentication
Y
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:X/V:D/RE:L/U:Amber

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 shiro-guice dependency usage
    Check project dependencies (Maven pom.xml, Gradle build.gradle, or JAR files) for the shiro-guice module presence
    Affected if shiro-guice dependency is present in the project
  2. Confirm web servlet context
    Examine the application deployment descriptor (web.xml) or servlet container configuration to determine if Shiro is configured within a javax.servlet context
    Affected if Shiro filter is configured in a web.xml or equivalent servlet context
  3. Check Apache Shiro version
    Inspect the shiro-core or shiro-web JAR manifest, or check the dependency management for the Shiro version number
    Affected if Shiro version is below 3.0.0 when shiro-guice is in use
  4. Verify Guice integration configuration
    Review Guice module configuration files (typically extending Abstract ShiroModule or using ShiroModule) for ShiroFilter registration in servlet context
    Affected if ShiroFilter is bound via Guice in a ServletContext and the version is below 3.0.0
  5. Review URL filter chain patterns
    Inspect shiro.ini or Shiro configuration for defined filter chains, particularly any catch-all or wildcard patterns that might be susceptible to path traversal bypass
    Affected if Filter chains use overly broad patterns (such as /**) without proper path normalization in a vulnerable Shiro version

User is affected if shiro-guice module is present in a web servlet context running Shiro versions prior to 3.0.0

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Apache Shiro to version 3.0.0 or later when using the shiro-guice module in a web servlet context to resolve this authentication bypass.

Recommended fix High confidence

Apache Shiro 3.0.0

  1. Update the shiro-guice dependency version in your build configuration (pom.xml, build.gradle, or equivalent) to version 3.0.0 or later
  2. Run your build to fetch the updated dependency
  3. Test the application thoroughly after upgrading to verify authentication works correctly in the web servlet context
  4. Verify that the shiro-guice module is properly initialized and that authentication bypass is resolved
Caveat Major version upgrade from 2.x to 3.0.0 may include breaking API changes; review release notes for migration steps

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56091 — 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-56091 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