Account Takeover via Session Fixation in Zitadel [Bypassing MFA]

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2024-28197: 0.34% estimated exploitation activity in the next 30 days; percentile 27.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact ZITADEL uses a cookie to identify the user agent (browser) and its user sessions. Although the cookie was handled according to best practices, it was accessible on subdomains of the ZITADEL instance. An attacker could take advantage of this and provide a malicious link hosted on the subdomain to the user to gain access to the victim’s account in certain scenarios. A possible victim would need to login through the malicious link for this exploit to work. If the possible victim already had the cookie present, the attack would not succeed. The attack would further only be possible if there was an initial vulnerability on the subdomain. This could either be the attacker being able to control DNS or a XSS vulnerability in an application hosted on a subdomain. Patches 2.x versions are fixed on = 2.46.0 2.45.x versions are fixed on = 2.45.1 2.44.x versions are fixed on = 2.44.3 ZITADEL recommends upgrading to the latest versions available in due course. Note that applying the patch…

Published by the source

11 Mar 2024, 21:25 UTC

Last modified by the source

7 Jan 2025, 18:36 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mq4x-r2w3-j7mr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-28197

Advisory: Account Takeover via Session Fixation in Zitadel [Bypassing MFA]
IDs: CVE-2024-28197, GHSA-mq4x-r2w3-j7mr
Record: https://patchnext.com/advisories/cve-2024-28197 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 2.45.1, 2.44.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected < 2.44.3; >= 2.45.0, < 2.45.1; fixed in 2.44.3, 2.45.1

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mq4x-r2w3-j7mr (GitHub-reviewed advisory GHSA-mq4x-r2w3-j7mr lists affected ranges: Go github.com/zitadel/zitadel >=0 =2.45.0 <2.45.1)

Commands are suggestions: review each one before running it.