Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.4

ZITADEL Allows Unauthorized Access After Organization or Project Deactivation

CVE-2024-47060GHSA-jj94-6f5c-65r8

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/zitadel/zitadel/v2 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/zitadel/zitadel/v2

    Affected
    >= 2.62.0, < 2.62.1>= 2.61.0, < 2.61.1>= 2.60.0, < 2.60.2>= 2.59.0, < 2.59.3>= 2.58.0, < 2.58.5>= 2.57.0, < 2.57.5>= 2.56.0, < 2.56.6>= 2.55.0, < 2.55.8< 2.54.10
    Fixed in
    2.58.5, 2.60.2, 2.55.8, 2.59.3, 2.57.5, 2.54.10, 2.61.1, 2.62.1, 2.56.6

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-jj94-6f5c-65r8 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.62.0 =2.61.0 =2.60.0 =2.59.0 =2.58.0 =2.57.0 =2.56.0 =2.55.0 =0 <2.54.10

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.4 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2024-47060: 0.36% estimated exploitation activity in the next 30 days; percentile 29.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-jj94-6f5c-65r8

Agent brief

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

# Patch Next advisory brief: CVE-2024-47060

Advisory: ZITADEL Allows Unauthorized Access After Organization or Project Deactivation
IDs: CVE-2024-47060, GHSA-jj94-6f5c-65r8
Record: https://patchnext.com/advisories/cve-2024-47060 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
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/v2 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel/v2: affected >= 2.62.0, < 2.62.1; >= 2.61.0, < 2.61.1; >= 2.60.0, < 2.60.2; >= 2.59.0, < 2.59.3; >= 2.58.0, < 2.58.5; >= 2.57.0, < 2.57.5; >= 2.56.0, < 2.56.6; >= 2.55.0, < 2.55.8; < 2.54.10; fixed in 2.58.5, 2.60.2, 2.55.8, 2.59.3, 2.57.5, 2.54.10, 2.61.1, 2.62.1, 2.56.6

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel/v2: 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/v2.
- 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-jj94-6f5c-65r8 (GitHub-reviewed advisory GHSA-jj94-6f5c-65r8 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.62.0 =2.61.0 =2.60.0 =2.59.0 =2.58.0 =2.57.0 =2.56.0 =2.55.0 =0 <2.54.10)

Commands are suggestions: review each one before running it.

Loading voting…