Servers and applications
GHSA-jh92-5mrj-p2w2
Unauthenticated Account Takeover Through Predictable Session IDs
- Severity
- High 8.1
- Published
- 28 Sept 2026
- Last changed
- 28 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.19.2
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H- Sources
- Project advisories (GitHub)
Description
ZITADEL’s hosted Login V2 UI allowed an unauthenticated attacker to obtain a fresh session token for another user’s authenticated session — including every factor that user had completed, such as MFA — without a password, a second factor, an existing session token, or any interaction with the victim, provided the attacker could guess the victim’s session ID. Session IDs are time-ordered identifiers, so an attacker who creates sessions shortly before and after the victim signs in can narrow the candidates to a small set and test them.
Login V2 kept its session references in a browser cookie that was neither signed nor otherwise validated. When updating a session, the login UI forwarded the session ID from that cookie to the session API using its own service-user credentials, which hold the session.write permission; the session API accepts such updates without the session’s current token and returns a newly issued one.
Workarounds
The recommended solution is to upgrade to a patched version. There is no configuration that fully closes this gap on unpatched versions. As a partial mitigation, rate limiting requests to the login UI (for example at a reverse proxy) reduces the feasibility of the session-ID search but does not close the gap.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-jh92-5mrj-p2w2
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-jh92-5mrj-p2w2