MediumGHSA-cvw9-c57h-3397CVE-2024-39683GO-2024-2968

ZITADEL Vulnerable to Session Information Leakage

Published 5 Jul 2024 · Updated 10 Sept 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 packages

Affected
>=2.0.0 <2.53.8
Fixed in
2.53.8
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.53.8
Affected
>=2.54.0 <2.54.5
Fixed in
2.54.5
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.54.5
Affected
>=2.55.0 <2.55.1
Fixed in
2.55.1
Update to the fixed version for your release line, for example:go get github.com/zitadel/zitadel@v2.55.1

Details

Impact

ZITADEL provides users the ability to list all user sessions of the current user agent (browser) by API and in the Console UI.

Due to a missing check, user sessions without that information (e.g. when created though the session service) were incorrectly listed exposing potentially other user's sessions.

Note that the Login UI was never affected and there was no possibility to take over such a session.

Patches

2.x versions are fixed on >= 2.55.1 2.54.x versions are fixed on >= 2.54.5 2.53.x versions are fixed on >= 2.53.8

ZITADEL recommends upgrading to the latest versions available in due course.

Workarounds

There is no workaround since a patch is already available.

References

  • https://github.com/zitadel/zitadel/pull/8231
  • https://discord.com/channels/927474939156643850/1254096852937347153
  • https://github.com/zitadel/zitadel/issues/8213

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 @cybertransformer, @Avolicious, @AmirhoseinBrz and @srividyaj for finding and reporting the vulnerability.

Is GHSA-cvw9-c57h-3397 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.