CVE-2026-43827
Analyzed Analyzed - Analysis Complete

Session Fixation in Apache Shiro

Publication date: 2026-05-25

Last updated on: 2026-05-28

Assigner: Apache Software Foundation

Description
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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-05-25
Last Modified
2026-05-28
Generated
2026-07-06
AI Q&A
2026-05-26
EPSS Evaluated
2026-07-04
NVD
CVE-2026-43827
EUVD
EUVD-2026-31736

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
apache shiro 3.0.0
apache shiro to 2.1.1 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-384 Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Impact Analysis

The vulnerability can allow an attacker to hijack a user's session by exploiting the fact that the session ID does not change upon login.

This can lead to unauthorized access to user accounts and sensitive information.

Executive Summary

This vulnerability is a session fixation issue found in default configurations of Apache Shiro versions from 1.0 to 2.1.0 and 3.0.0-alpha-1.

In the affected versions, when a user logs in successfully, the existing session is not invalidated and no new session with a new ID is created.

This means an attacker could potentially fixate a session ID and hijack a user's session.

Mitigation Strategies

To mitigate the session fixation vulnerability in Apache Shiro, users are recommended to upgrade to version 2.1.1 or 3.0.0-alpha-2 or later, as these versions fix the issue.

The vulnerability arises because in affected versions (1.0 to 2.1.0 and 3.0.0-alpha-1), when a session already exists, it is not invalidated upon successful login, nor is a new session generated with a new ID.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-43827. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart