Skip to content
Fencer Vulns
high 8.1

CVE-2023-49097 json

ZITADEL vulnerable account takeover via malicious host header injection

published 2023-11-29 2 y ago modified 2026-09-10 1 mo ago also GHSA-2wmj-46rj-qm2w , EUVD-2023-2852

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

ZITADEL is an identity infrastructure system. ZITADEL uses the notification triggering requests Forwarded or X-Forwarded-Host header to build the button link sent in emails for confirming a password reset with the emailed code. If this header is overwritten and a user clicks the link to a malicious site in the email, the secret code can be retrieved and used to reset the users password and take over his account. Accounts with MFA or Passwordless enabled can not be taken over by this attack. This issue has been patched in versions 2.41.6, 2.40.10 and 2.39.9.

Patch / fix

  • go github.com/zitadel/zitadel 2.39.9, 2.40.10, 2.41.6
  • zitadel zitadel 2.39.9, 2.40.10, 2.41.6

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
23 mo ago

Exploit prediction

0.77% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-2wmj-46rj-qm2w referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/zitadel/zitadel
>=2.39.0, <2.39.9
>=2.40.0, <2.40.10
>=2.41.0, <2.41.6
2.39.9
2.40.10
2.41.6

Affected products

  • zitadel zitadel

Classification

Weakness
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.