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

CVE-2026-7307 — keycloak-saml-core

HIGHFix: keycloak/keycloak#49119

CVE-2026-7307 is a high-severity (CVSS 7.5) CWE-1286 vulnerability in org.keycloak:keycloak-saml-core. A fix is available for org.keycloak:keycloak-saml-core — see the affected versions and patch details below.

Keycloak: keycloak: denial of service via specially crafted saml input

Also known asBIT-keycloak-2026-7307GHSA-p5mv-gj8j-xqgf
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 16, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • 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-2026-7307.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.46%0.92%1.38%0.1%0.9%Jun 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

1 pkg affected
☕org.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 was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial of Service (DoS) where the server becomes unavailable.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-saml-coreall versions26.6.2org.keycloak:keycloak-saml-core:26.6.2

Affected Products

1 product · 1 configurations
Application
build of keycloakredhat
≥ 26.4 && < 26.4.12
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-saml-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 HatImportant

This is a High severity denial of service vulnerability in Keycloak. An unauthenticated attacker with network access can send specially crafted XML input to the SAML endpoint, causing high CPU utilization and worker thread exhaustion, which renders the Keycloak server unavailable. This directly impacts the…

Workaround published by Red Hat
To mitigate this vulnerability, restrict network access to the Keycloak SAML endpoint to trusted networks and clients. Implement firewall rules to limit inbound connections to the Keycloak service port (e.g., 8080) from untrusted sources. If the SAML protocol is not required for your deployment, consider disabling it to eliminate the attack surface. Applying these network restrictions or configuration changes may necessitate a restart or reload of the Keycloak service, which could temporarily affect its availability.
Source: Red Hat security advisory for CVE-2026-7307 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Keycloak 26.2rhbk/keycloak-operator-bundle:26.2.16-1RHSA-2026:19595
Red Hat build of Keycloak 26.2.16rhbk/keycloak-rhel9RHSA-2026:19594
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.12-1RHSA-2026:19597
Red Hat build of Keycloak 26.4.12rhbk/keycloak-rhel9RHSA-2026:19596
Red Hat Single Sign-On 7.6.13keycloak-servicesRHSA-2026:76132
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el7ssoRHSA-2026:76128
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el8ssoRHSA-2026:76129
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el9ssoRHSA-2026:76130

Frequently Asked Questions

A flaw was found in Keycloak. A remote, unauthenticated attacker can send a specially crafted XML input to the Security Assertion Markup Language (SAML) endpoint. This malicious input can cause high CPU usage and worker thread starvation, leading to a Denial of Service (DoS) where the server becomes unavailable.
O3 Security · Impact-Aware SCA

Is CVE-2026-7307 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2026-7307: keycloak-saml-core DoS — Fixed in 26.6.2