Security readout for executives and security teams
Plain-English summary
Keycloak could accept tampered organization invitation tokens. A logged-in attacker with a legitimate invitation could change token details and register into an organization they should not access, potentially exposing protected identity-managed resources.
Executive priority
Treat as high priority where Keycloak organizations govern customer, tenant, or internal access. The issue can cross authorization boundaries and should be remediated promptly, even without confirmed active exploitation.
Technical view
CVE-2026-1529 is a CWE-347 signature-verification flaw in Red Hat build of Keycloak organization registration. The JWT invitation payload could be modified for organization ID and target email without cryptographic validation, enabling unauthorized organization self-registration.
Likely exposure
Exposure is most likely in Red Hat build of Keycloak 26.2 or 26.4 deployments using organization invitation-based registration, especially where organization membership grants sensitive application access.
Exploitation context
The bundle reports network access, low privileges, no user interaction, and high confidentiality and integrity impact. KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
The key weakness is missing cryptographic validation of invitation JWT payload claims. Evidence is limited to the supplied Red Hat and CVE records; no public exploit details or independent exploitation confirmation are included.
Mitigation direction
- Apply the relevant Red Hat advisories RHSA-2026:2363 through RHSA-2026:2366.
- Move affected 26.2 and 26.4 deployments to vendor-listed unaffected builds where applicable.
- Check Red Hat guidance for exact package and operator update paths.
- Temporarily tighten monitoring around organization invitations and new memberships.
- Review recent organization registrations for unexpected email or organization changes.
Validation and detection
- Inventory Red Hat build of Keycloak package names and versions.
- Compare keycloak-rhel9, operator, and operator-bundle versions against the affected list.
- Confirm organization invitation flows are not accepting modified JWT payload data.
- Review audit logs for suspicious organization self-registration events.
- Verify deployed builds match Red Hat unaffected status after patching.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1529 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhatCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N2.85.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Reported to Red Hat.
- Source timelineredhat
Reported to Red Hat.
- ADP timelineredhat-SADP
Made public.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-28T12:29:47.086Z: Reported to Red Hat.
- 2026-02-09T18:21:00.000Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:2363CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:2364CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:2365CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:2366CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-1529CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2433783CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1529.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.