Apache Shiro sends sensitive cookies in HTTPS session without 'Secure' attribute
CVE-2026-43828GHSA-c6r4-qjmw-cvj2
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.shiro:shiro-web 3.0.0-alpha-2, 2.2.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.apache.shiro:shiro-web
- Affected
- >= 1.0.0-incubating, < 2.2.0>= 3.0.0-alpha-1, <= 3.0.0-alpha-1
- Fixed in
- 2.2.0, 3.0.0-alpha-2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-c6r4-qjmw-cvj2 lists affected ranges: Maven org.apache.shiro:shiro-web >=1.0.0-incubating =3.0.0-alpha-1 <=3.0.0-alpha-1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/RE:L/U:Amber · score source
- EPSS
- CVE-2026-43828: 0.27% estimated exploitation activity in the next 30 days; percentile 19.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Default configurations of Apache Shiro send sensitive cookies in HTTPS session without 'Secure' attribute. 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, Shiro-native session manager, as well as Remember-Me manager sends JSESSIONID and rememberMe cookies without 'secure' attribute by default.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-c6r4-qjmw-cvj2
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-43828 Advisory: Apache Shiro sends sensitive cookies in HTTPS session without 'Secure' attribute IDs: CVE-2026-43828, GHSA-c6r4-qjmw-cvj2 Record: https://patchnext.com/advisories/cve-2026-43828 (revision 1, source checked 26 Oct 2026, 16:54 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.apache.shiro:shiro-web 3.0.0-alpha-2, 2.2.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.apache.shiro:shiro-web: affected >= 1.0.0-incubating, < 2.2.0; >= 3.0.0-alpha-1, <= 3.0.0-alpha-1; fixed in 2.2.0, 3.0.0-alpha-2 ## Suggested inspection (read-only) - Maven org.apache.shiro:shiro-web: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.apache.shiro:shiro-web. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-c6r4-qjmw-cvj2 (GitHub-reviewed advisory GHSA-c6r4-qjmw-cvj2 lists affected ranges: Maven org.apache.shiro:shiro-web >=1.0.0-incubating =3.0.0-alpha-1 <=3.0.0-alpha-1) Commands are suggestions: review each one before running it.
Loading voting…