NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2024-7341 — keycloak-services

HIGHFix: keycloak/keycloak@5e06da2

CVE-2024-7341 is a high-severity (CVSS 7.1) CWE-384 vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Wildfly-elytron: org.keycloak/keycloak-services: session fixation in elytron saml adapters

Also known asBIT-keycloak-2024-7341GHSA-5rxp-2rhr-qwqvGHSA-j76j-rqwj-jmvv
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-7341.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.30%1.12%1.93%2.75%2.2%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-servicesall versions22.0.12org.keycloak:keycloak-services:22.0.12
☕Mavenorg.keycloak:keycloak-services≥ 23.0.0&&< 24.0.724.0.7org.keycloak:keycloak-services:24.0.7
☕Mavenorg.keycloak:keycloak-services≥ 25.0.0&&< 25.0.525.0.5org.keycloak:keycloak-services:25.0.5

Affected Products

3 products · 5 configurations
Application
build of keycloakredhat
≥ 24.0 && < 24.0.7
range
Application
keycloakredhat
≤ 25.0.2
range
Application
single sign-onredhat
≥ 7.6 && < 7.6.10
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-services to 22.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-7341 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability is categorized as moderate severity rather than critical due to its specific exploitation conditions and impact. While it presents a session fixation risk, the attacker must first hijack a session before authentication. This pre-condition limits the exploitation vector to scenarios where an attacker…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-7341 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Build of Keycloakkeycloak-servicesRHSA-2024:6501
Red Hat Build of Keycloakkeycloak-servicesRHSA-2024:6503
Red Hat build of Keycloak 22rhbk/keycloak-operator-bundle:22.0.12-1RHSA-2024:6500
Red Hat build of Keycloak 24rhbk/keycloak-operator-bundle:24.0.7-4RHSA-2024:6502
Red Hat Single Sign-On 7keycloak-servicesRHSA-2024:6499
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el7ssoRHSA-2024:6493
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el8ssoRHSA-2024:6494
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el9ssoRHSA-2024:6495

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2024-7341 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2024-7341: keycloak-services — Fixed in 22.0.12