Cross-tenant user exposure via stale resource ownership
Published Jul 10, 2026 · Updated Jul 10, 2026
Improper access control in ZITADEL before 4.15.2 exposes a recreated user record to an administrator in the identifier's original tenant. After deletion, event-store validation retains the identifier's historical resource owner and routes later creation events with that ID to the former organization. The sequence requires accidental reuse of an exact deleted ID and cannot be forced or targeted, but the original tenant's administrator gains full access to the new record.
Summary
What happened
Improper access control in ZITADEL before 4.15.2 exposes a recreated user record to an administrator in the identifier's original tenant. After deletion, event-store validation retains the identifier's historical resource owner and routes later creation events with that ID to the former organization. The sequence requires accidental reuse of an exact deleted ID and cannot be forced or targeted, but the original tenant's administrator gains full access to the new record.
The record
- CVE
- CVE-2026-55670
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- ZITADEL
- Product
- ZITADEL
- Classifications
- CWE-639, CWE-284
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.15.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo