{"id":"CVE-2024-47060","aliases":["EUVD-2024-2823","GHSA-jj94-6f5c-65r8","GO-2024-3138"],"status":"published","title":"Unauthorized Access After Organization or Project Deactivation in Zitadel","description":"Zitadel is an open source identity management platform. 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. 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. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.","severity":{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00357,"percentile":0.29828,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-200","CWE-672","CWE-863"],"published":"2024-09-19T16:08:38Z","modified":"2026-10-28T02:30:56Z","fixes":[{"ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","fixed_in":["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"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.62.0"},{"fixed":"2.62.1"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.61.0"},{"fixed":"2.61.1"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.60.0"},{"fixed":"2.60.2"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.59.0"},{"fixed":"2.59.3"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.58.0"},{"fixed":"2.58.5"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.57.0"},{"fixed":"2.57.5"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.56.0"},{"fixed":"2.56.6"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.55.0"},{"fixed":"2.55.8"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.54.10"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.62.0"},{"fixed":"2.62.1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.61.0"},{"fixed":"2.61.1"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.60.0"},{"fixed":"2.60.2"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.59.0"},{"fixed":"2.59.3"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.58.0"},{"fixed":"2.58.5"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.57.0"},{"fixed":"2.57.5"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.56.0"},{"fixed":"2.56.6"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"2.55.0"},{"fixed":"2.55.8"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel/v2","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.54.10"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/zitadel/zitadel","ranges":[{"type":"SEMVER","events":[{"introduced":"0"}]}]}],"products":[{"vendor":"zitadel","product":"zitadel"}],"references":[{"url":"https://github.com/zitadel/zitadel/security/advisories/GHSA-jj94-6f5c-65r8","tags":["x_refsource_CONFIRM","Patch","Vendor Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-47060","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-jj94-6f5c-65r8"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47060.json","tags":["advisory"]},{"url":"https://github.com/zitadel/zitadel","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2024-47060","title":"Unauthorized Access After Organization or Project Deactivation in Zitadel","description":"Zitadel is an open source identity management platform. 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. 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. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.","status":"published","published":"2024-09-19T23:08:01.375Z","modified":"2024-09-20T15:28:08.556Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T14:33:57.302325Z"}],"euvd":[{"id":"EUVD-2024-2823","description":"Zitadel is an open source identity management platform. 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. 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. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.","status":"published","published":"2024-09-19T23:08:01Z","modified":"2024-09-20T15:28:08Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"updated_at":"2026-11-03T00:28:17.874342Z"}],"ghsa":[{"id":"GHSA-jj94-6f5c-65r8","title":"ZITADEL Allows Unauthorized Access After Organization or Project Deactivation","description":"### Summary\nIn 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.\nAdditionally, if a project was deactivated access to applications was also still possible.\n\n### Details\nThe 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.\n\n### PoC\n- Create a new Organization, create new project and setup OpenID connect.\n- Deactivate an Organization\n- Setup authentication without selecting Check for Project on Authentication\n- User is able to login despite the organization is deactivated\n\n### Impact\nThis vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation.\n\n### Patches\n\n2.x versions are fixed on \u003e= [2.62.1](https://github.com/zitadel/zitadel/releases/tag/v2.62.1)\n2.61.x versions are fixed on \u003e= [2.61.1](https://github.com/zitadel/zitadel/releases/tag/v2.61.1)\n2.60.x versions are fixed on \u003e= [2.60.2](https://github.com/zitadel/zitadel/releases/tag/v2.60.2)\n2.59.x versions are fixed on \u003e= [2.59.3](https://github.com/zitadel/zitadel/releases/tag/v2.59.3)\n2.58.x versions are fixed on \u003e= [2.58.5](https://github.com/zitadel/zitadel/releases/tag/v2.58.5)\n2.57.x versions are fixed on \u003e= [2.57.5](https://github.com/zitadel/zitadel/releases/tag/v2.57.5)\n2.56.x versions are fixed on \u003e= [2.56.6](https://github.com/zitadel/zitadel/releases/tag/v2.56.6)\n2.55.x versions are fixed on \u003e= [2.55.8](https://github.com/zitadel/zitadel/releases/tag/v2.55.8)\n2.54.x versions are fixed on \u003e= [2.54.10](https://github.com/zitadel/zitadel/releases/tag/v2.54.10)\n\n### Workaround\nUnpatched versions can explicitly disable the application to make sure the client is not allowed anymore.\n\n### Questions\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\nThanks to @prdp1137 for reporting this!\n","status":"published","published":"2024-09-19T16:08:38Z","modified":"2024-11-18T16:27:16Z","cvss":[{"version":"4.0","score":7.4,"vector":"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","level":"high"},{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-200","CWE-672"],"updated_at":"2026-11-02T14:38:20.833758Z"}],"nvd":[{"id":"CVE-2024-47060","description":"Zitadel is an open source identity management platform. 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. 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. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.","status":"published","published":"2024-09-20T00:15:03.767Z","modified":"2026-06-17T07:56:28.267Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"primary"}],"cwes":["CWE-200","CWE-863"],"updated_at":"2026-11-02T14:10:27.456509Z"}],"osv":[{"id":"CVE-2024-47060","title":"Unauthorized Access After Organization or Project Deactivation in Zitadel","description":"Zitadel is an open source identity management platform. 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. 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. This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. Versions 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, and 2.54.10 have been released which address this issue. Users are advised to upgrade. Users unable to upgrade may explicitly disable the application to make sure the client is not allowed anymore.","status":"published","published":"2024-09-19T23:08:01.375Z","modified":"2026-10-28T02:30:56.941886483Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","level":"medium"}],"cwes":["CWE-200"],"updated_at":"2026-11-02T15:44:43.253252Z"},{"id":"GHSA-jj94-6f5c-65r8","title":"ZITADEL Allows Unauthorized Access After Organization or Project Deactivation","description":"### Summary\nIn 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.\nAdditionally, if a project was deactivated access to applications was also still possible.\n\n### Details\nThe 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.\n\n### PoC\n- Create a new Organization, create new project and setup OpenID connect.\n- Deactivate an Organization\n- Setup authentication without selecting Check for Project on Authentication\n- User is able to login despite the organization is deactivated\n\n### Impact\nThis vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation.\n\n### Patches\n\n2.x versions are fixed on \u003e= [2.62.1](https://github.com/zitadel/zitadel/releases/tag/v2.62.1)\n2.61.x versions are fixed on \u003e= [2.61.1](https://github.com/zitadel/zitadel/releases/tag/v2.61.1)\n2.60.x versions are fixed on \u003e= [2.60.2](https://github.com/zitadel/zitadel/releases/tag/v2.60.2)\n2.59.x versions are fixed on \u003e= [2.59.3](https://github.com/zitadel/zitadel/releases/tag/v2.59.3)\n2.58.x versions are fixed on \u003e= [2.58.5](https://github.com/zitadel/zitadel/releases/tag/v2.58.5)\n2.57.x versions are fixed on \u003e= [2.57.5](https://github.com/zitadel/zitadel/releases/tag/v2.57.5)\n2.56.x versions are fixed on \u003e= [2.56.6](https://github.com/zitadel/zitadel/releases/tag/v2.56.6)\n2.55.x versions are fixed on \u003e= [2.55.8](https://github.com/zitadel/zitadel/releases/tag/v2.55.8)\n2.54.x versions are fixed on \u003e= [2.54.10](https://github.com/zitadel/zitadel/releases/tag/v2.54.10)\n\n### Workaround\nUnpatched versions can explicitly disable the application to make sure the client is not allowed anymore.\n\n### Questions\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\nThanks to @prdp1137 for reporting this!\n","status":"published","published":"2024-09-19T16:08:38Z","modified":"2024-11-18T16:27:15Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","level":"medium"},{"version":"4.0","score":7.4,"vector":"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","level":"high"}],"cwes":["CWE-200","CWE-672"],"updated_at":"2026-11-02T15:46:50.687609Z"},{"id":"GO-2024-3138","title":"ZITADEL Allows Unauthorized Access After Organization or Project Deactivation in github.com/zitadel/zitadel","description":"ZITADEL Allows Unauthorized Access After Organization or Project Deactivation in github.com/zitadel/zitadel.\n\nNOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.\n\n(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)\n\nThe additional affected modules and versions are: github.com/zitadel/zitadel before v2.54.10, from v2.55.0 before v2.55.8, from v2.56.0 before v2.56.6, from v2.57.0 before v2.57.5, from v2.58.0 before v2.58.5, from v2.59.0 before v2.59.3, from v2.60.0 before v2.60.2, from v2.61.0 before v2.61.1, from v2.62.0 before v2.62.1.","status":"published","published":"2024-09-26T18:24:03Z","modified":"2024-09-26T18:57:35.112925Z","updated_at":"2026-11-02T15:47:01.453823Z"}]}}