NVD / CVE Program· CNA GitHub_M

CVE-2025-64717: ZITADEL vulnerable to Account Takeover with deactivated Instance IdP

Noroxi assessment

Priority: Monitor (action score 29/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.49% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: github.com/zitadel/zitadel (Go) 1.80.0-v2.20.0.20251112124840-33c51deb2040, 2.71.19, 3.4.4.

Low priority for now. Upgrade to github.com/zitadel/zitadel (Go) 1.80.0-v2.20.0.20251112124840-33c51deb2040, 2.71.19, 3.4.4 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. Starting in version 2.50.0 and prior to versions 2.71.19, 3.4.4, and 4.6.6, a vulnerability in ZITADEL's federation process allowed auto-linking users from external identity providers to existing users in ZITADEL even if the corresponding IdP was not active or if the organization did not allow federated authentication. This vulnerability stems from the platform's failure to correctly check or enforce an organization's specific security settings during the authentication flow. An Organization Administrator can explicitly disable an IdP or disallow federation, but this setting was not being honored during the auto-linking process. This allowed an unauthenticated attacker to initiate a login using an IdP that should have been disabled for that organization. The platform would incorrectly validate the login and, based on a matching criteria, link the attacker's external identity to an existing internal user account. This may result in a full Account Takeover, bypassing the organization's mandated security controls. Note that accounts with MFA enabled can not be taken over by this attack. Also note that only IdPs create on an instance level would allow this to work. IdPs registered on another organization would always be denied in the (auto-)linking process. Versions 4.6.6, 3.4.4, and 2.71.19 resolve the issue by correctly validating the organization's login policy before auto-linking an external user. No known workarounds are available aside from upgrading.

HighCVSS 7.4 · v4.0—No exploit Fix available

Auth bypass

Published: Nov 13, 2025
Updated: Oct 19, 2026
EPSS: 0.4% · 42th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.4; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA: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 zitadel2.50.0 and later · before 2.71.19
zitadel zitadel3.0.0 and later · before 3.4.4
zitadel zitadel4.0.0 and later · before 4.6.6

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
- >= 4.0.0-rc.1, < 4.6.6, >= 3.0.0-rc.1, < 3.4.4, >= 2.50.0, < 2.71.19affected

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 1.80.0-v2.20.0.20240403060621-5b3946b67ef6 · before 1.80.0-v2.20.0.20251112124840-33c51deb2040	1.80.0-v2.20.0.20251112124840-33c51deb2040
Go	github.com/zitadel/zitadel	from 2.50.0 · before 2.71.19	2.71.19
Go	github.com/zitadel/zitadel	from 3.0.0-rc.1 · before 3.4.4	3.4.4
Go	github.com/zitadel/zitadel	from 4.0.0-rc.1 · before 4.6.6	4.6.6

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-2025-64103Oct 29, 2025 · Zitadel Bypass Second Authentication Factor
34Monitor
← EarlierCVE-2025-64431Nov 7, 2025 · IDOR Vulnerabilities in ZITADEL's Organization API allows Cross-Tenant Data Tempering
34Monitor
Later →CVE-2025-67494Dec 9, 2025 · ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login
34Monitor

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	1.80.0-v2.20.0.20251112124840-33c51deb2040	Package registry (OSV)
Go:github.com/zitadel/zitadel	2.71.19	Package registry (OSV)
Go:github.com/zitadel/zitadel	3.4.4	Package registry (OSV)
Go:github.com/zitadel/zitadel	4.6.6	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-2026-109372333 days apartZITADEL 3.0.0 before 4.19.2 Account Takeover via SAML Identity-Provider Confusion
37Monitor
CVE-2026-105210325 days apartZITADEL before 4.17.1 Unauthenticated MFA Enrollment via Login V1 Init Handlers
35Monitor
CVE-2026-105213325 days apartZITADEL before 4.17.1 Authentication Bypass via Login V2 for Deactivated Organizations
35Monitor
CVE-2025-6410315 days apartZitadel Bypass Second Authentication Factor
34Monitor
CVE-2026-105212325 days apartZITADEL before 3.4.14 and 4.16.2 Account Takeover via Passkey Enrollment
34Monitor
CVE-2026-29193114 days apartZITADEL: Bypassing Zitadel Login Behavior and Security Policy in Login V2
32Monitor

Chain candidates

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

CVE-2026-27945104 days apartZITADEL has potential SSRF via Actions
8Monitor

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.
Administrator privileges are required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: High
User interaction: None
Scope: X

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

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

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

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

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/releases/tag/v2.71.19

Show all references (3 more)

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

All records