LowGHSA-6x8v-2fq5-2229CVE-2026-55670GO-2026-5197

ZITADEL: Cross-Tenant User Leakage via Recycled Identifiers

Published 18 Jun 2026 · Updated 25 Jun 2026

Is your project on an affected github.com/zitadel/zitadel?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.80.0-v2.20.0.20260615092437-6082e59d47c1
Fixed in
1.80.0-v2.20.0.20260615092437-6082e59d47c1
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20260615092437-6082e59d47c1

Details

Summary

A flaw in the user lifecycle enforcement allowed deleted users to retain their original organization/tenant association. Recreating a deleted user under a distinct organization can cause the new user instance to be incorrectly provisioned within the original organization if the previous ID would be used to recreate it.

Impact

When a user is created, the system maps the generated or provided ID to its target organization (Org A). When that user is subsequently deleted, a deletion event is appended to the stream, but the historical mapping of the resource owner within the event store's validation layer is not cleared.

If a new user is later provisioned in a different organization (Org B) using that exact same ID, the event store validation logic reads the stream's history, matches it to the original organization, and routes the new user's events to Org A instead of Org B.

This issue represents a localized multi-tenancy isolation anomaly rather than an easily exploitable attack vector. Because the new user instance is incorrectly routed and provisioned inside Org A instead of Org B, an administrator from Org A inadvertently gains full access to this new user record.

However, there is no technical mechanism for a malicious actor to force, automate, or target this behavior against a specific user or tenant. Because the scenario relies entirely on an accidental sequence of operational events and requires the recycling of a highly specific ID space, the practical security risk is exceptionally low.

Affected Versions

Systems running one of the following versions are affected:

  • 4.x: 4.0.0 through 4.15.1 (including RC versions)
  • 3.x: 3.0.0 through 3.4.11 (including RC versions)

Patches

The vulnerability has been addressed in the latest releases. The patch resolves the issue by requiring the correct permission in case the verification flag is provided and only allows self-management of the email address, resp. phone number itself.

Workarounds

The recommended solution is to upgrade to a patched version.

Questions

If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)

Credits

Thanks to Charlie Graven from Famedly for reporting this vulnerability.

Is GHSA-6x8v-2fq5-2229 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/zitadel/zitadel, and gives you the command that fixes it.

More advisories for github.com/zitadel/zitadel

  • LowCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 in github.com/zitadel/zitadel · 1 Oct 2026
  • LowCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() in github.com/zitadel/zitadel · 1 Oct 2026
  • HighCVE-2026-85056ZITADEL: MFA bypass via session reuse in Login V2 · 24 Sept 2026
  • HighCVE-2026-85057ZITADEL: Actions V1 sandbox escape: host file read via require() · 24 Sept 2026
  • LowCVE-2026-56665ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider in github.com/zitadel/zitadel · 16 Sept 2026
  • LowCVE-2026-56666ZITADEL: Auto-linking by email: IdP-side email verification is not checked in github.com/zitadel/zitadel · 16 Sept 2026
All 93 advisories for github.com/zitadel/zitadel

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.