Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-8698

HIGH

CVE-2024-8698 is a high-severity (CVSS 7.7) CWE-347 vulnerability in org.keycloak:keycloak-saml-core. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2024-8698 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Keycloak-saml-core: improper verification of saml responses leading to privilege escalation in keycloak

Also known asGHSA-xgfv-xpx8-qhcr
Published
Sep 19, 2024
Updated
Jul 16, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known

Blast Radius

3 pkgs affected
org.keycloak:keycloak-saml-coreorg.keycloak:keycloak-saml-coreorg.keycloak:keycloak-saml-core

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 flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class. The method incorrectly determines whether a SAML signature is for the full document or only for specific assertions based on the position of the signature in the XML document, rather than the Reference element used to specify the signed element. This flaw allows attackers to create crafted responses that can bypass the validation, potentially leading to privilege escalation or impersonation attacks.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.keycloak:keycloak-saml-coreall versions22.0.13
Mavenorg.keycloak:keycloak-saml-core23.0.0&&< 24.0.824.0.8
Mavenorg.keycloak:keycloak-saml-core25.0.0&&< 25.0.625.0.6
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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-saml-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

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

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-8698 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-8698. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw exists in the SAML signature validation method within the Keycloak XMLSignatureUtil class. The method incorrectly determines whether a SAML signature is for the full document or only for specific assertions based on the position of the signature in the XML document, rather than the Reference element used to specify the signed element. This flaw allows attackers to create crafted responses that can bypass the validation, potentially leading to privilege escalation or impersonation attacks.
O3 Security · Impact-Aware SCA

Is CVE-2024-8698 in your dependencies?

O3 detects CVE-2024-8698 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.