CVE-2026-43828
Session Cookie Missing Secure Attribute in Apache Shiro
Publication date: 2026-05-25
Last updated on: 2026-05-25
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | shiro | From 1.0 (inc) to 2.1.1 (exc) |
| apache | shiro | 2.1.0 |
| apache | shiro | 3.0.0-alpha-1 |
| apache | shiro | 2.1.1 |
| apache | shiro | 3.0.0-alpha-2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-614 | The Secure attribute for sensitive cookies in HTTPS sessions is not set. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs because default configurations of Apache Shiro send sensitive cookies, specifically JSESSIONID and rememberMe cookies, in HTTPS sessions without the 'Secure' attribute.
Without the 'Secure' attribute, these cookies can be transmitted over unencrypted HTTP connections, potentially exposing them to interception by attackers.
The issue affects Apache Shiro versions from 1.0 to 2.1.0 and 3.0.0-alpha-1. It is fixed in versions 2.1.1 and 3.0.0-alpha-2 or later.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability involves Apache Shiro sending sensitive cookies in HTTPS sessions without the 'Secure' attribute by default. This can lead to the exposure of session cookies over insecure channels, potentially allowing attackers to hijack user sessions.
Such exposure of sensitive session information can negatively impact compliance with common data protection standards and regulations like GDPR and HIPAA, which require appropriate safeguards to protect personal and sensitive data during transmission.
Therefore, the vulnerability may increase the risk of non-compliance with these regulations due to insufficient protection of session cookies.
How can this vulnerability impact me? :
The vulnerability can lead to sensitive session cookies being exposed over insecure connections, increasing the risk of session hijacking.
An attacker who intercepts these cookies could impersonate a legitimate user, gaining unauthorized access to the user's session and potentially sensitive information.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, users are recommended to upgrade Apache Shiro to version 2.1.1, or 3.0.0-alpha-2 or later, which fixes the issue.