dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-7307

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 26.4.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A remote, unauthenticated attacker can send specially crafted XML input to Keycloak's SAML endpoint, causing excessive CPU consumption and worker thread starvation, resulting in denial of service.

MitigationImplement XML parser protections such as entity expansion limits, DOCTYPE restrictions, and XML bomb defenses on the SAML endpoint. Consider adding rate limiting and request size constraints as additional layers of protection.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:>= 26.4, < 26.4.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Keycloak is present
    Check for Keycloak processes or services running on the host (e.g., ps aux | grep keycloak, or check for keycloak-related services/containers)
    Affected if Keycloak is not installed - not affected
  2. Determine the installed version of Red Hat Build of Keycloak
    Run rpm -qa | grep keycloak or check the Keycloak version via the admin console or kc.sh --version command
    Affected if Version is >= 26.4 and < 26.4.12 - potentially affected
  3. Confirm SAML protocol is enabled in the realm
    Access Keycloak admin console, navigate to the realm, and check under Realm Settings > Login settings or Authentication > Flows for SAML bindings, or inspect realm configuration files for SAML identity providers
    Affected if SAML is not configured or enabled - not affected
  4. Verify the SAML endpoint is network-accessible
    Review firewall rules, network segmentation, or reverse proxy configurations to determine if the /auth/realms/*/protocol/saml or /realms/*/protocol/saml endpoint is exposed externally
    Affected if SAML endpoint is reachable from untrusted networks - at risk

Environment is affected if running Red Hat Build of Keycloak version 26.4 through 26.4.11 with SAML protocol enabled and the SAML endpoint exposed to network attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 26.4.12 or later
Fixed in 26.4.12
Interim mitigation

Implement XML parser protections such as entity expansion limits, DOCTYPE restrictions, and XML bomb defenses on the SAML endpoint. Consider adding rate limiting and request size constraints as additional layers of protection.

Recommended fix High confidence

26.4.12 or later

  1. Identify the currently running Keycloak version (must be >= 26.4 and < 26.4.12)
  2. Plan the upgrade during a maintenance window
  3. Backup the Keycloak database and configuration
  4. Stop the Keycloak server
  5. Upgrade Keycloak to version 26.4.12 or later
  6. Verify the upgrade was successful
  7. Restart the Keycloak server
  8. Test that the SAML endpoint responds normally under load
Caveat Standard patch upgrade; review release notes for any minor behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7307 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data