CVE-2024-29891: ZITADEL Improper Content-Type Validation Leads to Account Takeover via Stored XSS + CSP Bypass
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.76% (FIRST EPSS); higher than 55.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: zitadel zitadel 2.48.3.
Low priority for now. Upgrade to zitadel zitadel 2.48.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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. This vulnerability is fixed in 2.48.3, 2.47.8, 2.46.5, 2.45.5, 2.44.7, 2.43.11, and 2.42.17.
- Published
- Mar 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-434
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 8.7
- CNA · GitHub_M
- 8.7
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| zitadel | zitadel | cpe:2.3:a:zitadel:zitadel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
zitadel zitadel
- < 2.42.17, >= 2.43.0, < 2.43.11, >= 2.44.0, < 2.44.7, >= 2.45.0, < 2.45.5, >= 2.46.0, < 2.46.5, >= 2.47.0, < 2.47.8, >= 2.48.0, < 2.48.3affected
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- zitadel zitadelbefore 2.42.17
- zitadel zitadel2.43.0 and later · before 2.43.11
- zitadel zitadel2.44.0 and later · before 2.44.7
- zitadel zitadel2.45.0 and later · before 2.45.5
- zitadel zitadel2.46.0 and later · before 2.46.5
- zitadel zitadel2.47.0 and later · before 2.47.8
- zitadel zitadel2.48.0 and later · before 2.48.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/zitadel/zitadel | from 0 | — |
| Go | github.com/zitadel/zitadel | from 2.43.0 · before 2.43.11 | 2.43.11 |
| Go | github.com/zitadel/zitadel | from 2.44.0 · before 2.44.7 | 2.44.7 |
| Go | github.com/zitadel/zitadel | from 2.45.0 · before 2.45.5 | 2.45.5 |
| Go | github.com/zitadel/zitadel | from 2.46.0 · before 2.46.5 | 2.46.5 |
| Go | github.com/zitadel/zitadel | from 2.47.0 · before 2.47.8 | 2.47.8 |
| Go | github.com/zitadel/zitadel | from 2.48.0 · before 2.48.3 | 2.48.3 |
| Go | github.com/zitadel/zitadel | before 2.42.17 | 2.42.17 |
Same product
zitadel: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-109372ZITADEL 3.0.0 before 4.19.2 Account Takeover via SAML Identity-Provider Confusion37Monitor
- CVE-2026-105215ZITADEL before 4.16.2 Account Pre-Hijacking via Forged External IdP Callback37Monitor
- CVE-2026-105209ZITADEL before 3.4.15 and 4.17.1 Cross-Organization Account Takeover via Passkey Enrollment37Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-28197Mar 11, 2024 · Account Takeover via Session Fixation in Zitadel [Bypassing MFA]30Monitor
- ← EarlierCVE-2024-28855Mar 18, 2024 · ZITADEL vulnerable to improper HTML sanitization24Monitor
- Later →CVE-2024-29892Mar 27, 2024 · ZITADEL's actions can overload reserved claims19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| zitadel zitadel | 2.48.3 · description | Vendor (CNA) |
| Go:github.com/zitadel/zitadel | 2.42.17 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.43.11 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.44.7 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.45.5 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.46.5 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.47.8 | Package registry (OSV) |
| Go:github.com/zitadel/zitadel | 2.48.3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-434 · Unrestricted Upload of File with Dangerous TypeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/zitadel/zitadel/releases/tag/v2.43.11
- github.com/zitadel/zitadel/releases/tag/v2.44.7
- github.com/zitadel/zitadel/releases/tag/v2.45.5
- github.com/zitadel/zitadel/releases/tag/v2.46.5
- github.com/zitadel/zitadel/releases/tag/v2.47.8
- github.com/zitadel/zitadel/releases/tag/v2.48.3
- github.com/zitadel/zitadel/security/advisories/GHSA-hr5w-cwwq-2v4m
Vendor advisories and official records. Exploit/PoC links are deliberately left out.