ZITADEL's actions can overload reserved claims

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-29892: 0.77% estimated exploitation activity in the next 30 days; percentile 55.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. 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.

Published by the source

28 Mar 2024, 17:07 UTC

Last modified by the source

18 Nov 2024, 16:26 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gp8g-f42f-95q2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-29892

Advisory: ZITADEL's actions can overload reserved claims
IDs: CVE-2024-29892, GHSA-gp8g-f42f-95q2
Record: https://patchnext.com/advisories/cve-2024-29892 (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/zitadel/zitadel 2.48.3, 2.47.8, 2.46.5, 2.45.5, 2.44.7, 2.43.11, 2.42.17. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected < 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.3; fixed in 2.43.11, 2.47.8, 2.46.5, 2.42.17, 2.45.5, 2.44.7, 2.48.3

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gp8g-f42f-95q2 (GitHub-reviewed advisory GHSA-gp8g-f42f-95q2 lists affected ranges: Go github.com/zitadel/zitadel >=0 =2.43.0 =2.44.0 =2.45.0 =2.46.0 =2.47.0 =2.48.0 <2.48.3)

Commands are suggestions: review each one before running it.