HighGHSA-3rmw-76m6-4gjcCVE-2024-49757GO-2024-3217

User Registration Bypass in Zitadel

Published 25 Oct 2024 · Updated 28 Oct 2024

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 packages

Affected
>=2.63.0 <2.63.5
Fixed in
2.63.5
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.63.5
Affected
>=2.62.0 <2.62.7
Fixed in
2.62.7
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.62.7
Affected
>=2.61.0 <2.61.4
Fixed in
2.61.4
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.61.4
Affected
>=2.60.0 <2.60.4
Fixed in
2.60.4
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.60.4
Affected
>=2.59.0 <2.59.5
Fixed in
2.59.5
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.59.5
Affected
<2.58.7
Fixed in
2.58.7
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.58.7

Details

Impact

Zitadel allows administrators to disable the user self-registration. Due to a missing security check in versions prior to 2.63.4, disabling the "User Registration allowed" option only hid the registration button on the login page. Users could bypass this restriction by directly accessing the registration URL (/ui/login/loginname) and register a user that way.

Patches

2.x versions are fixed on >= 2.64.0 2.63.x versions are fixed on >= 2.63.5 2.62.x versions are fixed on >= 2.62.7 2.61.x versions are fixed on >= 2.61.4 2.60.x versions are fixed on >= 2.60.4 2.59.x versions are fixed on >= 2.59.5 2.58.x versions are fixed on >= 2.58.7

Workarounds

Updating to the patched version is the recommended solution.

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 @sevensolutions and @evilgensec for disclosing this!

Is GHSA-3rmw-76m6-4gjc 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.