Keycloak does not invalidate sessions when "Remember Me" is disabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2025-11429: 0.24% estimated exploitation activity in the next 30 days; percentile 14.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A flaw was found in Keycloak. Keycloak does not immediately enforce the disabling of the "Remember Me" realm setting on existing user sessions. Sessions created while "Remember Me" was active retain their extended session lifetime until they expire, overriding the administrator's recent security configuration change. This is a logic flaw in session management increases the potential window for successful session hijacking or unauthorized long-term access persistence. The flaw lies in the session expiration logic relying on the session-local "remember-me" flag without validating the current realm-level configuration.

Published by the source

23 Oct 2025, 15:30 UTC

Last modified by the source

17 Feb 2026, 17:20 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-64w3-5q9m-68xf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-11429

Advisory: Keycloak does not invalidate sessions when "Remember Me" is disabled
IDs: CVE-2025-11429, GHSA-64w3-5q9m-68xf
Record: https://patchnext.com/advisories/cve-2025-11429 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.keycloak:keycloak-services 26.4.1, 26.2.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.keycloak:keycloak-services: affected >= 26.3.0, < 26.4.1; < 26.2.11; fixed in 26.4.1, 26.2.11

## Suggested inspection (read-only)
- Maven org.keycloak:keycloak-services: 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.keycloak:keycloak-services.
- 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-64w3-5q9m-68xf (GitHub-reviewed advisory GHSA-64w3-5q9m-68xf lists affected ranges: Maven org.keycloak:keycloak-services >=26.3.0 =0 <26.2.11)

Commands are suggestions: review each one before running it.