Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

GHSA-v859-c572-qh5p

MediumCVSS 5.5 / 10
Published Sep 14, 2026·Last modified Sep 14, 2026
Affected Components(1)
Go logogithub.com/zitadel/zitadel
< 4.16.0
Description

Summary

A bug in how ZITADEL updates permissions when multiple project roles are deleted at the same time can cause some user permissions to be missed. This issue specifically affects User Grants on Granted Projects (projects shared between different organizations), potentially allowing users to keep access rights that were supposed to be completely removed.

Impact

When an organization shares a project with another organization (a Project Grant), administrators can assign specific roles to users via a User Grant. If multiple roles are deleted from that project at the same time, a background process runs to strip those roles from the assigned users.

Because of an error in how ZITADEL loops through a user's list of roles during this specific cross-organization cleanup, deleting two or more roles at once might cause the system to accidentally skip over some of them.

Scope Note: This vulnerability only affects User Grants on Granted Projects. Direct project roles and global organization roles are not impacted.

The risk depends entirely on what the skipped role allowed the user to do—if it was an administrative or high-privilege role, the user could potentially retain those elevated permissions within that granted project even after the role was officially deleted.

Affected Versions

  • 4.x: 4.0.0 through 4.15.3 (including RC versions)
  • 3.x: 3.0.0 through 3.4.12 (including RC versions)

Note: The 3.x release channel has reached End-of-Life (EOL) for security updates and will not receive a backported patch.

Patches & Resolution

This issue has been fully resolved in the latest releases.

The update fixes the role-removal logic to ensure no roles are skipped. Furthermore, this patch includes an automatic database migration. When you update, the system will automatically scan your database, find any user permissions on granted projects that may have been accidentally left behind by this bug, and correct them.

  • 4.x: Upgrade to $\ge$4.16.0
  • 3.x: Update to $\ge$4.16.0 (or check out workarounds)

Workarounds

There are no configuration workarounds. Upgrading to a patched version is the recommended solution and only way to trigger the automatic cleanup migration. If you cannot upgrade immediately, we recommend manually reviewing user permissions specifically for your Granted Projects where multiple roles were recently deleted.

Questions

If you have any questions or comments about this advisory, please reach out to us at security@zitadel.com.

Credits

Thanks to AyushParkara for reporting this vulnerability.

Upload your SBOM

Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.

Risk Scores
Base Score
5.5

The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs high-level or administrative privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the confidentiality of the information. There is a high impact on the integrity of the data.

Threat Intelligence
5.1

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.40%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard