CVE-2024-47060Public exploitNetwork attack vector

Unauthorized access via uncoupled resource deactivation

Published Sep 19, 2024 · Updated Sep 20, 2024

Incorrect authorization in affected ZITADEL 2.x releases allows remote attackers to access applications after deactivation. Deactivation changes an organization or project state without propagating that state to associated applications, so their authentication paths remain active. Exploitation requires a deactivated organization or project with an enabled application; the documented path also disables the project-on-authentication check, permitting login and access to resources intended to be inactive.

CVSS severity6.8
Medium
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in affected ZITADEL 2.x releases allows remote attackers to access applications after deactivation. Deactivation changes an organization or project state without propagating that state to associated applications, so their authentication paths remain active. Exploitation requires a deactivated organization or project with an enabled application; the documented path also disables the project-on-authentication check, permitting login and access to resources intended to be inactive.

The record

CVE
CVE-2024-47060
Published
Sep 19, 2024
Updated
Sep 20, 2024
Vendor
ZITADEL
Product
ZITADEL
Classifications
CWE-863, CWE-200, T1078
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Sep 20, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.54.10
  2. Affected versionversion=>= 2.55.0, < 2.55.8
  3. Affected versionversion=>= 2.56.0, < 2.56.6
  4. Affected versionversion=>= 2.57.0, < 2.57.5
  5. Affected versionversion=>= 2.58.0, < 2.58.5
  6. Affected versionversion=>= 2.59.0, < 2.59.3
  7. Affected versionversion=>= 2.60.0, < 2.60.2
  8. Affected versionversion=>= 2.61.0, < 2.61.1
  9. Affected versionversion=>= 2.62.0, < 2.62.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

ZITADEL · ZITADELversion=< 2.54.10; version=>= 2.55.0, < 2.55.8; version=>= 2.56.0, < 2.56.6; version=>= 2.57.0, < 2.57.5; version=>= 2.58.0, < 2.58.5; version=>= 2.59.0, < 2.59.3; version=>= 2.60.0, < 2.60.2; version=>= 2.61.0, < 2.61.1; version=>= 2.62.0, < 2.62.1

Published CVSS scores

6.8GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
6.5NISTCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1078Valid Accounts

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo