CVE-2026-76081: ZITADEL: Improper Role Revocation on Granted Projects during Multiple Role Deletions
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.
Published Sep 14, 2026
Affected packages
github.com/zitadel/zitadel
- Ecosystem
- Go
- Affected
- < 4.16.0
- Fixed in
- 4.16.0
- Check
go list -m github.com/zitadel/zitadel
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.0through4.15.3(including RC versions) - 3.x:
3.0.0through3.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.
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 [email protected].
Credits
Thanks to AyushParkara for reporting this vulnerability.
Credited to AyushParkara, IAM-marco, livio-a.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-85056
ZITADEL: MFA bypass via session reuse in Login V2
high8.2Sep 24, 2026CVE-2026-85057
ZITADEL: Actions V1 sandbox escape: host file read via require()
high8.7Sep 24, 2026CVE-2026-56668
ZITADEL: Unauthorized Token Privilege Escalation in OAuth2 Token Exchange
high8.1Sep 14, 2026CVE-2026-56665
ZITADEL: Missing Token Expiration (`exp`) Validation in JWT IdP Provider
medium4.2Sep 11, 2026CVE-2026-56666
ZITADEL: Auto-linking by email: IdP-side email verification is not checked
medium4.8Sep 11, 2026CVE-2026-54693
ZITADEL Users Can Self-Verify Email/Phone via API
high8.2No fixJul 29, 2026
