GHSA-hr5w-cwwq-2v4m
HIGHZITADEL's Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass
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.
Blast Radius
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.17 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.43.0&&< 2.43.11 | 2.43.11 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.44.0&&< 2.44.7 | 2.44.7 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.45.0&&< 2.45.5 | 2.45.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.46.0&&< 2.46.5 | 2.46.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.47.0&&< 2.47.8 | 2.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-hr5w-cwwq-2v4m 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 pinpoints whether GHSA-hr5w-cwwq-2v4m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hr5w-cwwq-2v4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hr5w-cwwq-2v4m in your dependencies?
O3 detects GHSA-hr5w-cwwq-2v4m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.