CVE-2026-1529: Org.keycloak.services.resources.organizations: keycloak: unauthorized organization registration via improper invitation token validation

Published Jan 28, 2026
·
Updated

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.

Other sources

Organization invitation tokens in Keycloak are parsed without cryptographic signature verification during the registration flow. This allows an attacker to take a legitimate invitation, modify the organization ID (orgid) and the target email (eml) within the JWT payload, and successfully self-register into an unauthorized organization.

Red Hat

Affected Software

4 affected componentsFixes available
Red Hat Keycloak
maven/org.keycloak:keycloak-services>=26.3.0<26.4.9
26.4.9
maven/org.keycloak:keycloak-services<26.2.13
26.2.13
maven/org.keycloak:keycloak-services>=26.5.0<26.5.3
26.5.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.4.9
  2. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.2.13
  3. Upgrade

    Upgrade maven/org.keycloak:keycloak-services to a version that resolves this vulnerability.

    Fixed in 26.5.3

Event History

Jan 28, 2026
Data Sourced
via Red Hat·12:31 PM
DescriptionSeverityAffected Software
Feb 9, 2026
CVE Published
via MITRE·06:36 PM
Data Sourced
via MITRE·06:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-1529?

CVE-2026-1529 has been classified as a high severity vulnerability due to its potential for unauthorized organization registration.

2

How do I fix CVE-2026-1529?

To fix CVE-2026-1529, update your Red Hat Keycloak installation to the latest version that addresses this vulnerability.

3

Who is affected by CVE-2026-1529?

Organizations using Red Hat Keycloak are affected by CVE-2026-1529 if they utilize invitation tokens without proper validation measures.

4

What type of attack does CVE-2026-1529 allow?

CVE-2026-1529 allows an attacker to exploit improper invitation token validation, enabling unauthorized organization registration.

5

What mitigation steps can be taken for CVE-2026-1529?

Mitigation steps for CVE-2026-1529 include ensuring proper validation of invitation tokens and monitoring for unauthorized access attempts.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203