CVE-2025-64717

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2025-175316 (ENISA EUVD) · GHSA-j4g7-v4m4-77px (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 13, 2025

Last Modified

October 19, 2026

Advisory Details (4)

Auto-updated Oct 27, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Account Takeover with deactivated Instance IdP · Advisory · zitadel/zitadel · GitHub

https://github.com/zitadel/zitadel/security/advisories/GHSA-j4g7-v4m4-77px
GitHub release Patch Available

v4.6.6

Patch available: zitadel/zitadel v4.6.6

https://github.com/zitadel/zitadel/releases/tag/v4.6.6
GitHub release Patch Available

v3.4.4

Patch available: zitadel/zitadel v3.4.4

https://github.com/zitadel/zitadel/releases/tag/v3.4.4
GitHub release Patch Available

v2.71.19

Patch available: zitadel/zitadel v2.71.19

https://github.com/zitadel/zitadel/releases/tag/v2.71.19

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/zitadel/zitadel @ 4.6.6 (fixes >= 4.0.0-rc.1, < 4.6.6)—ghsa
gogithub.com/zitadel/zitadel @ 3.4.4 (fixes >= 3.0.0-rc.1, < 3.4.4)—ghsa
gogithub.com/zitadel/zitadel @ 2.71.19 (fixes >= 2.50.0, < 2.71.19)—ghsa
gogithub.com/zitadel/zitadel @ 1.80.0-v2.20.0.20251112124840-33c51deb2040 (fixes >= 1.80.0-v2.20.0.20240403060621-5b3946b67ef6, < 1.80.0-v2.20.0.20251112124840-33c51deb2040)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/zitadel/zitadel—
  • 4.0.0-rc.1 up to 4.6.6: fixed in 4.6.6
  • 3.0.0-rc.1 up to 3.4.4: fixed in 3.4.4
  • 2.50.0 up to 2.71.19: fixed in 2.71.19
  • 1.80.0-v2.20.0.20240403060621-5b3946b67ef6 up to 1.80.0-v2.20.0.20251112124840-33c51deb2040: fixed in 1.80.0-v2.20.0.20251112124840-33c51deb2040
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 219 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 21:19 UTCEG score recompute
  2. 2026-11-01 21:19 UTCGHSA enrichmentGHSA-j4g7-v4m4-77px · GitHub severity HIGH
  3. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  4. 2026-11-01 08:02 UTCGHSA enrichmentGHSA-j4g7-v4m4-77px · GitHub severity HIGH
  5. 2026-10-31 22:44 UTCEG score recompute
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-10-31 00:10 UTCEG score recompute
  8. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-10-30 01:36 UTCEG score recompute
  10. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-29 03:03 UTCEG score recompute
  12. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-10-28 04:28 UTCEG score recompute
  14. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-27 05:53 UTCEG score recompute
  16. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-26 03:15 UTCEG score recompute
  18. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-25 16:10 UTCEG score recompute
  20. 2026-10-25 04:38 UTCEG score recompute
  21. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-24 06:04 UTCEG score recompute
  23. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-10-23 07:28 UTCEG score recompute
  25. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 73 more
  1. 2026-10-22 08:51 UTCEG score recompute
  2. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-21 10:16 UTCEG score recompute
  4. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-20 11:41 UTCEG score recompute
  6. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-19 12:22 UTCEG score recompute
  8. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-18 05:20 UTCEG score recompute
  10. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-17 06:51 UTCEG score recompute
  12. 2026-10-16 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-16 08:15 UTCEG score recompute
  14. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-15 07:18 UTCEG score recompute
  16. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-14 03:17 UTCEG score recompute
  18. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-12 16:49 UTCEG score recompute
  20. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-11 20:24 UTCEG score recompute
  22. 2026-10-11 18:36 UTCEG score recompute
  23. 2026-10-11 15:10 UTCEG score recompute
  24. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  28. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  29. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  30. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  31. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  32. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  33. 2026-10-02 01:11 UTCOSV refresh
  34. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  35. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  36. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  37. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  38. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  39. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  40. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  42. 2026-09-19 15:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  43. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  45. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  46. 2026-09-15 03:10 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  48. 2026-09-12 18:36 UTCOSV refresh
  49. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  51. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  52. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  53. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  54. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  55. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  56. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  57. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  58. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  59. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  60. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  61. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  62. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  63. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  64. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  65. 2026-08-24 23:44 UTCOSV refresh
  66. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  67. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  68. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  69. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  70. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  71. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  72. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  73. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.5% · 38th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-64717?
CVE-2025-64717 is a critical-severity vulnerability; its CVE record was published on November 13, 2025. 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…
When was the CVE record for CVE-2025-64717 published?
The CVE record for CVE-2025-64717 was published on November 13, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-64717 actively exploited?
CVE-2025-64717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-64717?
CVE-2025-64717 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-64717?
A fix for CVE-2025-64717 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-64717

Explore →

Is Your Infrastructure Affected by CVE-2025-64717?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs