NVD / CVE Program· CNA GitHub_M

CVE-2024-47000: Service Users Deactivation not Working in Zitadel

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.41% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: github.com/zitadel/zitadel/v2 (Go) 2.55.8, 2.56.6, 2.57.5.

Low priority for now. Upgrade to github.com/zitadel/zitadel/v2 (Go) 2.55.8, 2.56.6, 2.57.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Zitadel is an open source identity management platform. ZITADEL's user account deactivation mechanism did not work correctly with service accounts. Deactivated service accounts retained the ability to request tokens, which could lead to unauthorized access to applications and resources. 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 t upgrade. Users unable to upgrade may instead of deactivating the service account, consider creating new credentials and replacing the old ones wherever they are used. This effectively prevents the deactivated service account from being utilized. Be sure to revoke all existing authentication keys associated with the service account and to rotate the service account's password.

HighCVSS 7.5 · v3.1—No exploit Fix available

Pre-auth

Published: Sep 19, 2024
Updated: Jun 17, 2026
EPSS: 0.4% · 35th percentile
CWE: CWE-269

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.5
CNA · GitHub_M: 8.1; 0.6 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
zitadel	zitadel	cpe:2.3:a:zitadel:zitadel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

zitadel zitadelbefore 2.54.10
zitadel zitadel2.55.0 and later · before 2.55.8
zitadel zitadel2.56.0 and later · before 2.56.6
zitadel zitadel2.57.0 and later · before 2.57.5
zitadel zitadel2.58.0 and later · before 2.58.5
zitadel zitadel2.59.0 and later · before 2.59.3
zitadel zitadel2.60.0 and later · before 2.60.2
zitadel zitadel2.61.0
zitadel zitadel2.62.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

zitadel zitadel
- >= 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.10affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	github.com/zitadel/zitadel	from 0	—
Go	github.com/zitadel/zitadel/v2	from 2.55.0 · before 2.55.8	2.55.8
Go	github.com/zitadel/zitadel/v2	from 2.56.0 · before 2.56.6	2.56.6
Go	github.com/zitadel/zitadel/v2	from 2.57.0 · before 2.57.5	2.57.5
Go	github.com/zitadel/zitadel/v2	from 2.58.0 · before 2.58.5	2.58.5
Go	github.com/zitadel/zitadel/v2	from 2.59.0 · before 2.59.3	2.59.3
Go	github.com/zitadel/zitadel/v2	from 2.60.0 · before 2.60.2	2.60.2
Go	github.com/zitadel/zitadel/v2	from 2.61.0 · before 2.61.1	2.61.1
Go	github.com/zitadel/zitadel/v2	from 2.62.0 · before 2.62.1	2.62.1
Go	github.com/zitadel/zitadel/v2	before 2.54.10	2.54.10

Same product

zitadel: all records

Other highest-scoring records for the same primary product.

CVE-2026-109372ZITADEL 3.0.0 before 4.19.2 Account Takeover via SAML Identity-Provider Confusion
37Monitor
CVE-2026-105215ZITADEL before 4.16.2 Account Pre-Hijacking via Forged External IdP Callback
37Monitor
CVE-2026-105209ZITADEL before 3.4.15 and 4.17.1 Cross-Organization Account Takeover via Passkey Enrollment
37Monitor

Published before and after this one in the same product

← EarlierCVE-2024-41953Jul 31, 2024 · Zitadel improperly sanitizes HTML in emails and Console UI
24Monitor
← EarlierCVE-2024-46999Sep 19, 2024 · User Grant Deactivation not Working in Zitadel
26Monitor
Later →CVE-2024-47060Sep 19, 2024 · Unauthorized Access After Organization or Project Deactivation in Zitadel
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Go:github.com/zitadel/zitadel/v2	2.54.10	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.55.8	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.56.6	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.57.5	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.58.5	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.59.3	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.60.2	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.61.1	Package registry (OSV)
Go:github.com/zitadel/zitadel/v2	2.62.1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-28197192 days apartAccount Takeover via Session Fixation in Zitadel [Bypassing MFA]
30Monitor
CVE-2024-469990 days apartUser Grant Deactivation not Working in Zitadel
26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-269 · Improper Privilege Management

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.

The bug in code

The whole CWE-269 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

yaml

1kind: ClusterRole
2rules:
3  - apiGroups: ["*"]
4    resources: ["*"]
5    verbs: ["*"]

Fixed

yaml

1kind: Role
2metadata:
3  namespace: lodos-system
4rules:
5  - apiGroups: ["apps"]
6    resources: ["deployments"]
7    verbs: ["get", "list", "update"]

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Abuse Elevation Control MechanismT1548

Change log

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/zitadel/zitadel/security/advisories/GHSA-qr2h-7pwm-h393

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records