How severe is CVE-2022-36051?

CVE-2022-36051 has a CVSS score of 8.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-36051?

CVE-2022-36051 affects the following packages: github.com/zitadel/zitadel (Go), github.com/zitadel/zitadel (Go). Ecosystems affected: Go.

How do I fix CVE-2022-36051?

Update github.com/zitadel/zitadel to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36051 is resolved across your whole dependency graph.

How do I detect CVE-2022-36051 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-36051 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-36051 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-36051 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-36051?

CVE-2022-36051 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-36051?

CVE-2022-36051 is classified as CWE-436 (CWE-436), CWE-863 (CWE-863). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-36051 published, and has it been updated?

CVE-2022-36051 was published on August 31, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-36051 — zitadel

HIGHFix: zitadel/zitadel#4237

CVE-2022-36051 is a high-severity (CVSS 8.7) CWE-436 vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.

Broken Authorization in ZITADEL Actions

Also known asGHSA-c8fj-4pm8-mp2c

Published

Aug 31, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36051.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs63th percentile — riskier than 63% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel

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

Actions, introduced in ZITADEL 1.42.0 on the API and 1.56.0 for Console, is a feature, where users with role ORG_OWNER 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

https://docs.zitadel.com/docs/guides/manage/customize/behavior https://docs.zitadel.com/docs/apis/actions https://zitadel.com/blog/pentest-results-h1-2021

Questions

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/zitadel/zitadel`	≥ 2.0.0&&< 2.2.0	2.2.0`go get github.com/zitadel/zitadel@v2.2.0`
🐹Go	`github.com/zitadel/zitadel`	≥ 1.42.0&&< 1.87.1	1.87.1`go get github.com/zitadel/zitadel@v1.87.1`

Affected Products

1 product · 2 configurations

Application

zitadelzitadel

≥ 2.0.0 && < 2.2.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel to 2.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36051 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact **Actions**, introduced in ZITADEL **1.42.0** on the API and **1.56.0** for Console, is a feature, where users with role `ORG_OWNER` 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.