dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-4630

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 26.4.12 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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. An authenticated client could exploit an Insecure Direct Object Reference (IDOR) vulnerability in the Authorization Services Protection API endpoint. By knowing or obtaining a resource's unique identifier (UUID) belonging to another Resource Server within the same realm, the client could bypass authorization checks. This allows the client to perform unauthorized GET, PUT, and DELETE operations on resources, leading to information disclosure and potential unauthorized modification or deletion of data.

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

Keycloak's Authorization Services Protection API contains an IDOR vulnerability where an authenticated client can access resources belonging to different Resource Servers within the same realm by directly referencing those resources' UUIDs. This bypasses authorization checks and allows unauthorized GET, PUT, and DELETE operations.

MitigationApply vendor patches when available. In the interim, implement compensating controls such as strict validation that resources belong to the requesting client's authorized Resource Server before processing any API request.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 the installed Keycloak version
    Check the Keycloak version through the admin console (Server info tab) or by examining the jar file name in the installation directory, or run: `kc.sh --version` from the Keycloak bin directory
    Affected if The installed version is 26.4.x and is lower than 26.4.12 (e.g., 26.4.0 through 26.4.11)
  2. Confirm Authorization Services is enabled
    In the Keycloak admin console, navigate to the target realm, then to Authorization > Settings. Verify that Enable Authorization Services is turned ON
    Affected if Authorization Services is enabled for the realm
  3. Verify Protection API is configured
    In the Keycloak admin console, go to Authorization > Settings > Protection API. Check if the Resource Server has the Protection API enabled and note the allowed origins and URLs
    Affected if The Protection API is enabled and accessible (even without explicit client configuration, the API endpoints exist in the authorization endpoint URL path)
  4. Check for cross-resource-server access patterns
    Review application logs and Keycloak audit logs for API calls to /auth/realms/{realm}/protocol/openid-connect/token and subsequent calls to /auth/realms/{realm}/authz/protection/resource_set/{resource_id} where the requesting client differs from the resource's owner Resource Server
    Affected if Any authenticated client is able to make GET, PUT, or DELETE calls to resources outside their own Resource Server by directly referencing UUIDs

You are affected if your Keycloak version is 26.4.x and is below 26.4.12 AND you have Authorization Services with the Protection API enabled for any realm.

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

Apply vendor patches when available. In the interim, implement compensating controls such as strict validation that resources belong to the requesting client's authorized Resource Server before processing any API request.

Recommended fix High confidence

Keycloak 26.4.12 or later

  1. 1. Back up your current Keycloak database and configuration files before proceeding with the upgrade.
  2. 2. Download Keycloak version 26.4.12 or later from the official Keycloak releases (keycloak.org) or your enterprise repository.
  3. 3. Stop the running Keycloak instance gracefully to avoid data corruption.
  4. 4. If using a managed upgrade, run the migration tools provided by your deployment method (e.g., Kubernetes operator, Docker, or manual installation).
  5. 5. Deploy the new Keycloak 26.4.12 (or later) binaries or container image.
  6. 6. Start the upgraded Keycloak instance and verify it starts successfully.
  7. 7. Test the Authorization Services Protection API to confirm the IDOR vulnerability is remediated - verify that cross-resource-server operations are properly denied.
  8. 8. Verify that existing client configurations and authorization policies still function correctly.
Caveat Review Keycloak 26.4.x release notes for any configuration or API changes; minor version upgrades typically have minimal breaking changes but should be tested in a staging environment first

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

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4630 — 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-4630 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