CVE-2026-1529

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2026-01-28 12:22 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-02-09 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-07-15 02:18 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.5% in the next 30 days (EPSS).
• Severity: 8.1 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2026-02-09 20:15 UTC

Last modified

2026-07-15 02:18 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-347

Record status

Deferred

Attack profile CVSS 3.1 · 8.1

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-1529.md and follow it. Check whether this project is affected by CVE-2026-1529. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge