Broken Authorization in ZITADEL Actions

Exploitation

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

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N

EPSS

• CVE-2022-36051: 1.01% estimated exploitation activity in the next 30 days; percentile 63.19 (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 Actions, introduced in ZITADEL 1.42.0 on the API and 1.56.0 for Console, is a feature, where users with role ORGOWNER are able to create Javascript Code, which is invoked by the system at certain points during the login. Actions, for example, allow creating authorizations (user grants) on newly created users programmatically. Due to a missing authorization check, Actions were able to grant authorizations for projects that belong to other organisations inside the same Instance. Granting authorizations via API and Console is not affected by this vulnerability. Patches 2.x versions are fixed on = 2.2.0 1.x versions are fixed on = 1.87.1 ZITADEL recommends upgrading to the latest versions available in due course. Workarounds There is no workaround since a patch is already available. Who did disclose this During our recurring white box penetration test our external security consultant found this issue. The full report will be made public after the complete review. References…

Published by the source

30 Aug 2022, 20:54 UTC

Last modified by the source

30 Jan 2023, 05:06 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c8fj-4pm8-mp2c

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

# Patch Next advisory brief: CVE-2022-36051

Advisory: Broken Authorization in ZITADEL Actions
IDs: CVE-2022-36051, GHSA-c8fj-4pm8-mp2c
Record: https://patchnext.com/advisories/cve-2022-36051 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.2.0, 1.87.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected >= 2.0.0, < 2.2.0; >= 1.42.0, < 1.87.1; fixed in 2.2.0, 1.87.1

## 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-c8fj-4pm8-mp2c (GitHub-reviewed advisory GHSA-c8fj-4pm8-mp2c lists affected ranges: Go github.com/zitadel/zitadel >=2.0.0 =1.42.0 <1.87.1)

Commands are suggestions: review each one before running it.