Skip to content

GHSA-hcvw-475w-8g7p CVE-2026-1529

Keycloak affected by improper invitation token validation

High Maven
Severity
8.1 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.49%
Chance of exploitation in the next 30 days. Higher than 42.42% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-347 Improper Verification of Cryptographic Signature
Fix
26.5.3
Upgrade org.keycloak:keycloak-services to this version or later

Description

A flaw was found in Keycloak. An attacker can exploit this vulnerability by modifying the organization ID and target email within a legitimate invitation token's JSON Web Token (JWT) payload. This lack of cryptographic signature verification allows the attacker to successfully self-register into an unauthorized organization, leading to unauthorized access.

Affected versions

Maven

PackageVulnerableFixed in
org.keycloak:keycloak-services
>= 26.5.0, < 26.5.3
26.5.3
org.keycloak:keycloak-services
< 26.2.13
26.2.13
org.keycloak:keycloak-services
>= 26.3.0, < 26.4.9
26.4.9

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.keycloak:keycloak-services Maven → 26.5.3

maven
<dependency><groupId>org.keycloak</groupId><artifactId>keycloak-services</artifactId><version>26.5.3</version></dependency>
gradle
implementation("org.keycloak:keycloak-services:26.5.3")

Severity breakdown

CVSS 3.1 8.1

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Weakness

CWE-347: Improper Verification of Cryptographic Signature

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-v3f7-2p4r-mwfw
Keycloak vulnerable to cross-site scripting (xss) via case-insensitive uri validation bypass
High Also affects org.keycloak:keycloak-services
GHSA-9jrw-8xf7-xqhq
Keycloak vulnerable to information disclosure through arbitrary filesystem path probing
Medium Also affects org.keycloak:keycloak-services
GHSA-w3p3-7cjg-vgfw
Keycloak allows unauthorized access to resources via uma permission ticket bypass
Medium Also affects org.keycloak:keycloak-services
GHSA-f5p5-6xmx-p252
Keycloak vulnerable to authorization bypass via incorrect uri comparison
High Also affects org.keycloak:keycloak-services
GHSA-r7rc-c989-86g6
Keycloak: Attacker can re-enable and take over disabled clients via registration access token
Medium Also affects org.keycloak:keycloak-services
GHSA-4gv3-mc9p-5wqc
Keycloak: Unauthenticated account takeover via reset-credentials flow bypass
Critical Also affects org.keycloak:keycloak-services
GHSA-6g26-7cx5-mrrg
Keycloak: Information disclosure due to user profile permission bypass
Low Also affects org.keycloak:keycloak-services
GHSA-cpf7-j4cf-vqx4
Keycloak has an Out-of-bounds Read
Medium Also affects org.keycloak:keycloak-services
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor