# CVE-2026-107623: Keycloak-services: keycloak-services: oidc dcr read-modify-write silently disables offline token revocation

> A serialization bug in Keycloak's OIDC DCR component silently disables offline token revocation, allowing tokens to remain valid after backchannel logout.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-qxj8-968q-qm7w

## What is CVE-2026-107623?

CVE-2026-107623 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the OIDC Dynamic Client Registration (DCR) component of Keycloak. A bug in the response serialization causes the backchannel logout offline token revocation setting to be omitted from responses. When a client performs a standard update, this missing information causes the setting to be silently disabled. As a result, offline tokens may remain valid even after a user session is terminated via backchannel logout.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-107623?


## How do I fix CVE-2026-107623?

No fix has been published for CVE-2026-107623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107623 being exploited?

There is no known exploitation of CVE-2026-107623 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107623 and fix it if it is affected.

What it is: CVE-2026-107623 is a medium-severity missing authorization vulnerability in Red Hat Build of Keycloak, published on 8 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107623 in the wild and no public exploit code.

Affected product: Red Hat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107623/ (Markdown: https://insights.sbomify.com/CVE-2026-107623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107623
- OSV: https://osv.dev/vulnerability/CVE-2026-107623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107623/
Summaries are generated and may contain mistakes; the official description above is the record.