dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-9705

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 26.4.13 / 26.6.4 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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's client registration service. A remote attacker, possessing a previously issued Registration Access Token (RAT), could exploit this vulnerability to re-enable a client that an administrator had explicitly disabled. This bypasses security controls, allowing the attacker to reset the client's secret and potentially regain privileged API access. The primary impact includes unauthorized information disclosure and potential integrity compromise.

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 · moderate confidence

A logic flaw in Keycloak's client registration service allows an attacker with a previously issued Registration Access Token (RAT) to bypass admin-disablement of a client and re-enable it. This enables the attacker to reset the client's secret and regain privileged API access, resulting in unauthorized information disclosure and potential integrity compromise.

MitigationApply the vendor patch for CVE-2026-9705 when available; in the interim, revoke all active RATs for disabled clients and monitor client state changes for suspicious re-enablement activity.

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.13>= 26.6, < 26.6.4

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 Keycloak version
    Run 'kc.sh --version' or 'kc.bat --version' from the Keycloak bin directory, or check the server startup logs for the version string
    Affected if The installed version falls within 26.4.0 to 26.4.12 OR 26.6.0 to 26.6.3 (the version range for Redhat Build Of Keycloak is >= 26.4, < 26.4.13 and >= 26.6, < 26.6.4)
  2. Confirm client registration service is in use
    Review your Keycloak realm configuration for clients using the dynamic client registration endpoint (typically /realms/{realm}/clients-registrations/openid-legacy or the default client registration endpoint), or check audit logs for API calls to /clients-registrations
    Affected if Client registration service endpoints are accessible and clients have been registered through this mechanism (the flaw requires the client registration service to be enabled and in use)
  3. Enumerate active Registration Access Tokens
    Query the Keycloak admin API endpoint GET /{realm}/clients/{client-uuid}/registration-access-token for all clients, or review your client configuration storage for stored RAT values
    Affected if Any active RAT exists for clients in the realm (the attack requires a previously issued RAT that remains valid after admin disablement)
  4. Review client state change audit logs
    Check Keycloak audit logs or server logs for entries showing a client being disabled via admin API followed by a state change that re-enables the same client, particularly if the re-enablement occurs via client registration endpoint rather than admin console
    Affected if Any client shows a disablement event followed by a re-enablement event that did not originate from admin console actions (indicating potential exploitation of the bypass flaw)

You are affected if your Keycloak version is within the vulnerable range AND clients are registered via the client registration service AND you have active RATs that could be used to re-enable disabled clients.

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.13 / 26.6.4 or later
Fixed in 26.4.1326.6.4
Interim mitigation

Apply the vendor patch for CVE-2026-9705 when available; in the interim, revoke all active RATs for disabled clients and monitor client state changes for suspicious re-enablement activity.

Recommended fix High confidence

Keycloak 26.4.13 or 26.6.4 (depending on your current branch)

  1. Back up your Keycloak database and configuration before upgrading
  2. If running Keycloak 26.4.x, upgrade to version 26.4.13 or later
  3. If running Keycloak 26.6.x, upgrade to version 26.6.4 or later
  4. After upgrade, verify that disabled clients cannot be re-enabled using a stale Registration Access Token (RAT)
  5. Confirm that client secret reset is properly blocked for disabled clients
Caveat Standard upgrade considerations apply; test in staging environment before production deployment

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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