dbcve.org
ShiroApplication · Apache

CVE-2026-43827

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-25
Fix available
A fix is available. Upgrade to 2.1.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Default configurations of Apache Shiro have a session fixation vulnerability. This issue affects Apache Shiro from 1.0 to 2.1.0, and 3.0.0-alpha-1. Users are recommended to upgrade to version 2.1.1, or 3.0.0-alpha-2 or later, which fixes the issue. In the affected versions, when a session already exists, it is not invalidated upon successful login, nor is a new session being generated with a new ID.

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 versions 1.0 through 2.1.0 and 3.0.0-alpha-1 contain a session fixation vulnerability where existing sessions are not invalidated and new session IDs are not generated upon successful login, potentially allowing attackers to hijack authenticated sessions.

MitigationUpgrade to Apache Shiro version 2.1.1 or 3.0.0-alpha-2 or later to receive the fix.

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.1.1= 3.0.0

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 installed Apache Shiro version
    Check the shiro-core JAR file name in your application libraries, or look for the version in pom.xml, build.gradle, or your dependency management file. Run 'jar tf shiro-core.jar | grep manifest' to read the manifest for version info.
    Affected if The version is 1.0 through 2.1.0, or equals 3.0.0-alpha-1
  2. Confirm session-based authentication is in use
    Examine your shiro.ini, shiro.ini.xml, or shiro-config.xml file for 'sessionManager' or 'session' related beans. Also check if your application uses SecurityUtils.getSubject().login() for authentication.
    Affected if Session management is configured and users authenticate via login method; the flaw does not apply to stateless token-based authentication
  3. Inspect session fixation protection setting
    Look for 'sessionFixationProtection' attribute in your Shiro session manager configuration. In shiro.ini this appears under [sessionManager] as 'sessionFixationProtection = none' or similar.
    Affected if The setting is absent, set to 'none', or missing entirely (defaulting to no protection in vulnerable versions)
  4. Test session behavior on login
    Deploy a test: obtain a session ID before authentication, authenticate, then observe whether the session ID changes and whether the original session becomes invalid. Compare behavior to expected secure behavior.
    Affected if Session ID remains the same after login, or the pre-login session remains valid and accessible after successful authentication

You are affected if you run Apache Shiro version 1.0-2.1.0 or 3.0.0-alpha-1, use session-based login, and observe no session ID change or session invalidation after authentication.

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.1.1 or later
Fixed in 2.1.1
Interim mitigation

Upgrade to Apache Shiro version 2.1.1 or 3.0.0-alpha-2 or later to receive the fix.

Recommended fix High confidence

2.1.1 or 3.0.0-alpha-2

  1. Identify the current Apache Shiro version in your project by checking your dependency management (Maven pom.xml, Gradle build.gradle, or similar)
  2. For Maven projects: Update the Shiro dependency version to 2.1.1 (or for 3.x line users: upgrade to 3.0.0-alpha-2 or later) by editing the pom.xml version element
  3. For Gradle projects: Update shiro-version in build.gradle to '2.1.1' (or '3.0.0-alpha-2' for 3.x line)
  4. Run your build and test suite to verify the upgrade does not introduce regressions
  5. Deploy the updated version to your environment

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

Fix this in Shiro Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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