NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2026-1529 — keycloak-services

HIGHFix: keycloak/keycloak#46155

CVE-2026-1529 is a high-severity (CVSS 8.1) CWE-347 vulnerability in org.keycloak:keycloak-services. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak affected by improper invitation token validation

Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-1529.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk
0.00%0.33%0.66%0.99%0.0%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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 Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-services≥ 26.5.0&&< 26.5.326.5.3org.keycloak:keycloak-services:26.5.3
☕Mavenorg.keycloak:keycloak-servicesall versions26.2.13org.keycloak:keycloak-services:26.2.13
☕Mavenorg.keycloak:keycloak-services≥ 26.3.0&&< 26.4.926.4.9org.keycloak:keycloak-services:26.4.9
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

0x240x23elu/CVE-2026-1529

Keycloak: Unauthorized organization registration via improper invitation

⭐ 6🍴 2Sep 2026

0xlyvio/CVE-2026-1529-Keycloak-Exploit-Tool

Keycloak: Unauthorized organization registration via improper invitation

⭐ 3🍴 0Sep 2026

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-services, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-services to 26.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1529 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This IMPORTANT flaw in Keycloak allows an attacker to register into an unauthorized organization. The vulnerability arises from improper cryptographic signature verification of organization invitation tokens, enabling modification of the organization ID and target email within the JWT payload.

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Source: Red Hat security advisory for CVE-2026-1529 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat build of Keycloak 26.2rhbk/keycloak-operator-bundle:26.2.13-1RHSA-2026:2364
Red Hat build of Keycloak 26.2.13rhbk/keycloak-rhel9RHSA-2026:2363
Red Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle:26.4.9-1RHSA-2026:2366
Red Hat build of Keycloak 26.4.9rhbk/keycloak-rhel9RHSA-2026:2365

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-1529 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2026-1529: keycloak-services — Fixed in 26.5.3