# CVE-2025-11429: Keycloak-server: too long and not settings compliant session

> Keycloak fails to immediately enforce disabled Remember Me settings on existing sessions, allowing persistent unauthorized access despite configuration changes.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Oct 2025
- **Updated:** 20 Jan 2026
- **Also known as:** ECHO-0db4-a794-6040, GHSA-64w3-5q9m-68xf, MINI-wm6g-3x62-qr8m

## What is CVE-2025-11429?

CVE-2025-11429 is a medium-severity vulnerability in Red Hat build of Keycloak 26.2, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-11429?

4 open source packages ship an affected version, including org.keycloak:keycloak-services.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.2.11 |
| `org.keycloak:keycloak-services` | Maven | All versions | 26.2.11 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.4.1 |
| `org.keycloak:keycloak-services` | Maven | From 26.3.0 | 26.4.1 |

## How do I fix CVE-2025-11429?

Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 26.2.11 or 26.4.1.

## Is CVE-2025-11429 being exploited?

There is no known exploitation of CVE-2025-11429 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-11429 and fix it if it is affected.

What it is: CVE-2025-11429 is a medium-severity vulnerability in Red Hat build of Keycloak 26.2, published on 23 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11429 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.11
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 26.2.11
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.4.1
- org.keycloak:keycloak-services (Maven): affected from 26.3.0; fixed in 26.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-11429/ (Markdown: https://insights.sbomify.com/CVE-2025-11429/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-11429
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-11429
- OSV: https://osv.dev/vulnerability/CVE-2025-11429

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-11429/
Summaries are generated and may contain mistakes; the official description above is the record.
