# CVE-2024-7341: Wildfly-elytron: org.keycloak/keycloak-services: session fixation in elytron saml adapters

> Attackers can hijack sessions before authentication due to unchanged session IDs in Keycloak SAML adapters, leading to account takeover.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Sep 2024
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-keycloak-2024-7341, GHSA-5rxp-2rhr-qwqv, GHSA-j76j-rqwj-jmvv

## What is CVE-2024-7341?

CVE-2024-7341 is a high-severity authentication bypass vulnerability in Redhat Build of Keycloak, published on 9 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2024-7341?

13 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 |
| `org.keycloak:keycloak-services` | Maven | All versions | 22.0.12 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 |
| `org.keycloak:keycloak-services` | Maven | From 23.0.0 | 24.0.7 |
| `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.5 |
| `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.5 |
| `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.5 |
| `org.keycloak:keycloak-services` | Maven | From 25.0.0 | 25.0.5 |
| `keycloak` | Bitnami | From 22.0.0 | 22.0.12, 24.0.7 |

Products: Redhat Build of Keycloak, Redhat Keycloak, Redhat Single Sign-On.

## How do I fix CVE-2024-7341?

Upgrade org.keycloak:keycloak-services to a fixed version for your release line: 22.0.12, 24.0.7 or 25.0.5.

## Is CVE-2024-7341 being exploited?

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

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7341 and fix it if it is affected.

What it is: CVE-2024-7341 is a high-severity authentication bypass vulnerability in Redhat Build of Keycloak, published on 9 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-7341 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12
- org.keycloak:keycloak-services (Maven): affected all versions; fixed in 22.0.12
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7
- org.keycloak:keycloak-services (Maven): affected from 23.0.0; fixed in 24.0.7
- org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.5
- org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.5
- org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.5
- org.keycloak:keycloak-services (Maven): affected from 25.0.0; fixed in 25.0.5

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-2024-7341/ (Markdown: https://insights.sbomify.com/CVE-2024-7341/index.md)
```

## Sources

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

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