Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7

Zitadel May Bypass Second Authentication Factor

CVE-2025-64103GHSA-cfjq-28r2-4jv5

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-cfjq-28r2-4jv5 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.53.6 =2.54.3 =2.55.0 =0 <1.80.0-v2.20.0.20251029091250-b284f8474eed

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-64103: 0.35% estimated exploitation activity in the next 30 days; percentile 28.94 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary A vulnerability in Zitadel's token verification prematurely marked sessions as authenticated when only one factor was verified. Impact Zitadel provides an API for managing sessions, enabling custom login experiences in a dedicated UI or direct integration into applications. Session Tokens are issued for active sessions, which can be used as Bearer tokens to call the Zitadel API. Starting from 2.55.0 (see other affected versions below), Zitadel only required multi factor authentication in case the login policy has either enabled requireMFA or requireMFAForLocalUsers. If a user has set up MFA without this requirement, Zitadel would consider single factor auhtenticated sessions as valid as well and not require multiple factors. Bypassing second authentication factors weakens multifactor authentication and enables attackers to bypass the more secure factor. An attacker can target the TOTP code alone, only six digits, bypassing password verification entirely and potentially…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-cfjq-28r2-4jv5

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64103

Advisory: Zitadel May Bypass Second Authentication Factor
IDs: CVE-2025-64103, GHSA-cfjq-28r2-4jv5
Record: https://patchnext.com/advisories/cve-2025-64103 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/zitadel/zitadel 1.80.0-v2.20.0.20251029091250-b284f8474eed; github.com/zitadel/zitadel/v2 2.71.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/zitadel/zitadel: affected < 1.80.0-v2.20.0.20251029091250-b284f8474eed; fixed in 1.80.0-v2.20.0.20251029091250-b284f8474eed
- Go github.com/zitadel/zitadel/v2: affected >= 2.53.6, <= 2.53.9; >= 2.54.3, <= 2.54.10; >= 2.55.0, <= 2.71.17; fixed in 2.71.18

## Suggested inspection (read-only)
- Go github.com/zitadel/zitadel: check the installed version with your package manager.
- Go github.com/zitadel/zitadel/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cfjq-28r2-4jv5 (GitHub-reviewed advisory GHSA-cfjq-28r2-4jv5 lists affected ranges: Go github.com/zitadel/zitadel/v2 >=2.53.6 =2.54.3 =2.55.0 =0 <1.80.0-v2.20.0.20251029091250-b284f8474eed)

Commands are suggestions: review each one before running it.

Loading voting…