How severe is GHSA-jj94-6f5c-65r8?

GHSA-jj94-6f5c-65r8 has a CVSS score of 6.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jj94-6f5c-65r8?

GHSA-jj94-6f5c-65r8 affects the following packages: github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), github.com/zitadel/zitadel/v2 (Go), and 1 more. Ecosystems affected: Go.

How do I fix GHSA-jj94-6f5c-65r8?

Update github.com/zitadel/zitadel/v2 to 2.62.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj94-6f5c-65r8 is resolved across your whole dependency graph.

How do I detect GHSA-jj94-6f5c-65r8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jj94-6f5c-65r8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jj94-6f5c-65r8?

O3 pinpoints whether GHSA-jj94-6f5c-65r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jj94-6f5c-65r8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jj94-6f5c-65r8 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 GHSA-jj94-6f5c-65r8?

GHSA-jj94-6f5c-65r8 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 27th 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.

When was GHSA-jj94-6f5c-65r8 published, and has it been updated?

GHSA-jj94-6f5c-65r8 was published on September 19, 2024 and was last updated on November 18, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-jj94-6f5c-65r8

MEDIUM

ZITADEL Allows Unauthorized Access After Organization or Project Deactivation

Also known asCVE-2024-47060GO-2024-3138

Published

Sep 19, 2024

Updated

Nov 18, 2024

Affected

9 pkgs

Patched

9 / 9

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk27th percentile+0.16%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

9 pkgs affected

🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2🐹github.com/zitadel/zitadel/v2+1 more

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

Summary

In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible.

Details

The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible.

PoC

Create a new Organization, create new project and setup OpenID connect.
Deactivate an Organization
Setup authentication without selecting Check for Project on Authentication
User is able to login despite the organization is deactivated

Impact

This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation.

Patches

2.x versions are fixed on >= 2.62.1 2.61.x versions are fixed on >= 2.61.1 2.60.x versions are fixed on >= 2.60.2 2.59.x versions are fixed on >= 2.59.3 2.58.x versions are fixed on >= 2.58.5 2.57.x versions are fixed on >= 2.57.5 2.56.x versions are fixed on >= 2.56.6 2.55.x versions are fixed on >= 2.55.8 2.54.x versions are fixed on >= 2.54.10

Workaround

Unpatched versions can explicitly disable the application to make sure the client is not allowed anymore.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

Credits

Thanks to @prdp1137 for reporting this!

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.62.0&&< 2.62.1	2.62.1
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.61.0&&< 2.61.1	2.61.1
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.60.0&&< 2.60.2	2.60.2
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.59.0&&< 2.59.3	2.59.3
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.58.0&&< 2.58.5	2.58.5
🐹Go	`github.com/zitadel/zitadel/v2`	≥ 2.57.0&&< 2.57.5	2.57.5

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/v2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/zitadel/zitadel/v2 to 2.62.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj94-6f5c-65r8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jj94-6f5c-65r8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jj94-6f5c-65r8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible. ### Details The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, lead

O3 Security · Impact-Aware SCA

Is GHSA-jj94-6f5c-65r8 in your dependencies?

O3 detects GHSA-jj94-6f5c-65r8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works