CVE-2026-1035: Keycloak services Keycloak Does Not Validate And Vulnerability

LOW
Advisory Identifier: GHSA-m2w5-7xhv-w6fh
CVSS 3.1
CWE-367
Published
Advisory Summary

CVE-2026-1035 is a LOW (CVSS 3.1) keycloak does not validate and vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting Keycloak services libraries in the Maven ecosystem. The issue involves keycloak does not validate and update refresh token usage atomically. Remediation is available in the latest vendor maintenance releases.

CVE-2026-1035 at a Glance

CVE Identifier CVE-2026-1035
GHSA Identifier GHSA-m2w5-7xhv-w6fh
Severity LOW
CVSS v3.1 Base Score 3.1
CWE Classification CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
Affected Product Keycloak services
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 3.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-1035

To remediate this vulnerability, upgrade all affected Keycloak services dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.keycloak:keycloak-services fixed: Latest secure release
<dependency>
    <groupId>org.keycloak</groupId>
    <artifactId>keycloak-services</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.keycloak

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-1035, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.keycloak

Analyze the terminal output to locate any version of Keycloak services in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.keycloak command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. In Keycloak services, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.

CVE-2026-1035 Affected Keycloak services Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
org.keycloak:keycloak-services
Maven
≤ 26.2.5

References

Frequently Asked Questions

What is CVE-2026-1035?
CVE-2026-1035 is a security vulnerability in Keycloak services involving Keycloak does not validate and update refresh token usage atomically under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition.
Which Keycloak services versions are affected?
Affected versions include releases prior to current release patches across affected packages: org.keycloak:keycloak-services.
What version fixes CVE-2026-1035?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is keycloak-services affected?
Yes, org.keycloak:keycloak-services is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-1035?
CVE-2026-1035 has a CVSS v3.1 base score of 3.1 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-1035?
CVE-2026-1035 is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition (The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.).
How can I check Maven dependencies for CVE-2026-1035?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.keycloak'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m2w5-7xhv-w6fh",
  "modified" : "2026-04-02T15:31:34Z",
  "published" : "2026-01-21T06:31:20Z",
  "aliases" : [ "CVE-2026-1035" ],
  "summary" : "Keycloak does not validate and update refresh token usage atomically",
  "details" : "A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.keycloak:keycloak-services"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "26.2.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-1035"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/keycloak/keycloak/issues/45647"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:6477"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/errata/RHSA-2026:6478"
  }, {
    "type" : "WEB",
    "url" : "https://access.redhat.com/security/cve/CVE-2026-1035"
  }, {
    "type" : "WEB",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2430314"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/keycloak/keycloak"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-367" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-21T22:29:46Z",
    "nvd_published_at" : "2026-01-21T06:15:46Z"
  }
}