ZITADEL is an open source identity management platform. Prior to 3.4.8 and 4.12.2, a vulnerability in Zitadel's Management API has been reported, which allowed authenticated users holding a valid low-privilege token (e.g., project.read, project.grant.read, or project.app.read) to retrieve management-plane information belonging to other organizations by specifying a different tenant’s project_id, grant_id, or app_id. This vulnerability is fixed in 3.4.8 and 4.12.2.
CVE-2026-32131
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(low)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity77% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/zitadel/zitadel/releases/tag/v3.4.8
- security-advisories@githubhttps://github.com/zitadel/zitadel/releases/tag/v4.12.2
- security-advisories@githubhttps://github.com/zitadel/zitadel/security/advisories/GHSA-wr6r-59xg-4pj2
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:37 UTCEG score recompute
Frequently asked(5)
What is CVE-2026-32131?
When was CVE-2026-32131 disclosed?
Is CVE-2026-32131 actively exploited?
What is the CVSS score of CVE-2026-32131?
How do I remediate CVE-2026-32131?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32131
Is Your Infrastructure Affected by CVE-2026-32131?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.