CVE-2024-29891 — zitadel
HIGHCVE-2024-29891 is a high-severity (CVSS 8.7) Unrestricted File Upload vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.
ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-29891.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-29891 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadelReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
ZITADEL users can upload their own avatar image and various image types are allowed.
Due to a missing check, an attacker could upload HTML and pretend it is an image to gain access to the victim's account in certain scenarios. A possible victim would need to directly open the supposed image in the browser, where a session in ZITADEL needs to be active for this exploit to work.
The exploit could only be reproduced if the victim was using Firefox. Chrome, Safari as well as Edge did not execute the code.
Patches
2.x versions are fixed on >= 2.48.3 2.47.x versions are fixed on >= 2.47.8 2.46.x versions are fixed on >= 2.46.5 2.45.x versions are fixed on >= 2.45.5 2.44.x versions are fixed on >= 2.44.7 2.43.x versions are fixed on >= 2.43.11 2.42.x versions are fixed on >= 2.42.17
ZITADEL recommends upgrading to the latest versions available in due course.
Workarounds
There is no workaround since a patch is already available.
References
None
Questions
If you have any questions or comments about this advisory, please email us at [email protected]
Credits
Thanks to Amit Laish – GE Vernova for finding and reporting the vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel | all versions | 2.42.17go get github.com/zitadel/zitadel@v2.42.17 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.43.0&&< 2.43.11 | 2.43.11go get github.com/zitadel/zitadel@v2.43.11 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.44.0&&< 2.44.7 | 2.44.7go get github.com/zitadel/zitadel@v2.44.7 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.45.0&&< 2.45.5 | 2.45.5go get github.com/zitadel/zitadel@v2.45.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.46.0&&< 2.46.5 | 2.46.5go get github.com/zitadel/zitadel@v2.46.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.47.0&&< 2.47.8 | 2.47.8go get github.com/zitadel/zitadel@v2.47.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel to 2.42.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-29891 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-29891 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-29891. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-29891 in your dependencies?
O3 Security finds CVE-2024-29891 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.