CVE-2024-29892: ZITADEL's actions can overload reserved claims
Impact Under certain circumstances an action could set reserved claims managed by ZITADEL. For example it would be possible to set the claim urn:zitadel:iam:user:resourceowner:name if it was not set by ZITADEL itself.
Published Mar 28, 2024 · Updated Nov 18, 2024
Affected packages
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- < 2.42.17
- Fixed in
- 2.42.17
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.43.0, < 2.43.11
- Fixed in
- 2.43.11
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.44.0, < 2.44.7
- Fixed in
- 2.44.7
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.45.0, < 2.45.5
- Fixed in
- 2.45.5
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.46.0, < 2.46.5
- Fixed in
- 2.46.5
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.47.0, < 2.47.8
- Fixed in
- 2.47.8
- Check
go list -m github.com/zitadel/zitadel
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- >= 2.48.0, < 2.48.3
- Fixed in
- 2.48.3
- Check
go list -m github.com/zitadel/zitadel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
Under certain circumstances an action could set reserved claims managed by ZITADEL.
For example it would be possible to set the claim urn:zitadel:iam:user:resourceowner:name
{"urn:zitadel:iam:user:resourceowner:name": "ACME"}if it was not set by ZITADEL itself.
To compensate for this we introduced a protection that does prevent actions from changing claims that start with urn:zitadel:iam
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
Workarounds
No workaround available since a patch is available
Credits
Many thanks to @schettn whose disclosure of another topic lead us to find this issue.
Credited to schettn, fforootd, adlerhurst, livio-a.
References
- https://github.com/zitadel/zitadel/security/advisories/GHSA-gp8g-f42f-95q2
- https://nvd.nist.gov/vuln/detail/CVE-2024-29892
- https://github.com/zitadel/zitadel/releases/tag/v2.42.17
- https://github.com/zitadel/zitadel/releases/tag/v2.43.11
- https://github.com/zitadel/zitadel/releases/tag/v2.44.7
- https://github.com/zitadel/zitadel/releases/tag/v2.45.5
- https://github.com/zitadel/zitadel/releases/tag/v2.46.5
- https://github.com/zitadel/zitadel/releases/tag/v2.47.8
- https://github.com/zitadel/zitadel/releases/tag/v2.48.3
- https://github.com/advisories/GHSA-gp8g-f42f-95q2
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85056
ZITADEL: MFA bypass via session reuse in Login V2
high8.2Sep 24, 2026CVE-2026-85057
ZITADEL: Actions V1 sandbox escape: host file read via require()
high8.7Sep 24, 2026CVE-2026-56668
ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange
high8.1Sep 14, 2026CVE-2026-76081
ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions
medium5.5Sep 14, 2026CVE-2026-56665
ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
medium4.2Sep 11, 2026CVE-2026-56666
ZITADEL: Auto-linking by email: IdP-side email verification is not checked
medium4.8Sep 11, 2026
