dbcve.org
ZitadelApplication

CVE-2025-53895

HIGH · 8.8 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to 2.70.14 / 2.71.13 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ZITADEL is an open source identity management system. Starting in version 2.53.0 and prior to versions 4.0.0-rc.2, 3.3.2, 2.71.13, and 2.70.14, vulnerability in ZITADEL's session management API allows any authenticated user to update a session if they know its ID, due to a missing permission check. This flaw enables session hijacking, allowing an attacker to impersonate another user and access sensitive resources. Versions prior to `2.53.0` are not affected, as they required the session token for updates. Versions 4.0.0-rc.2, 3.3.2, 2.71.13, and 2.70.14 fix the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ZITADEL identity management system versions 2.53.0 through versions prior to 4.0.0-rc.2, 3.3.2, 2.71.13, and 2.70.14 contain a missing authorization check in the session management API. Any authenticated user can update any session by knowing its ID, enabling session hijacking and impersonation of other users to access sensitive resources.

MitigationUpgrade ZITADEL to version 4.0.0-rc.2, 3.3.2, 2.71.13, or 2.70.14 to receive the patched version with proper permission validation on session update operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZitadelApplication
Affected:>= 2.53.0, < 2.70.14>= 2.71.0, < 2.71.13>= 3.0.0, < 3.3.1= 4.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify ZITADEL installation version
    Locate the installed ZITADEL version through the admin console, API endpoint, or command-line tool used to deploy or manage the instance
    Affected if The installed version falls within >= 2.53.0, < 2.70.14; >= 2.71.0, < 2.71.13; >= 3.0.0, < 3.3.1; or = 4.0.0
  2. Confirm session management API exposure
    Verify whether the session management API endpoints are accessible to authenticated users within your ZITADEL deployment
    Affected if Authenticated users can access session management API endpoints without additional authorization checks
  3. Check for session ID exposure
    Audit logs, access patterns, and API responses to determine whether session IDs for other users could be discovered or intercepted
    Affected if Session IDs are exposed in URLs, logs, or responses accessible to other authenticated users
  4. Review API authorization controls
    Examine the session update API endpoint configuration to verify whether the requester must own or be authorized for the session being modified
    Affected if The session update endpoint accepts any session ID from any authenticated user without ownership verification

Your environment is affected if ZITADEL is running a version between 2.53.0 and 4.0.0 (excluding the patched releases 2.70.14, 2.71.13, 3.3.2, and 4.0.0-rc.2) and the session management API is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.70.14 / 2.71.13 / 3.3.1 or later
Fixed in 2.70.142.71.133.3.1
Interim mitigation

Upgrade ZITADEL to version 4.0.0-rc.2, 3.3.2, 2.71.13, or 2.70.14 to receive the patched version with proper permission validation on session update operations.

Recommended fix High confidence

2.70.14 (for 2.53.x-2.70.x), 2.71.13 (for 2.71.x), 3.3.2 (for 3.0.x-3.3.x), or 4.0.0-rc.2/later (for 4.0.0)

  1. 1. Identify the currently running Zitadel version by checking the application logs or configuration
  2. 2. Determine which upgrade path applies based on current version: for 2.53.x-2.70.x upgrade to 2.70.14; for 2.71.x upgrade to 2.71.13; for 3.0.x-3.3.x upgrade to 3.3.2; for 4.0.0 upgrade to 4.0.0-rc.2 or later stable release
  3. 3. Review Zitadel release notes for the target version to understand changes and prerequisites
  4. 4. Backup the Zitadel database and configuration before upgrading
  5. 5. Stop the Zitadel service
  6. 6. Apply the upgrade following Zitadel's official upgrade documentation (typically involves replacing the binary or container image)
  7. 7. Verify the session management API now enforces proper permission checks
  8. 8. Restart the Zitadel service and confirm normal operation
Caveat Review release notes for potential breaking changes between versions; major version jumps (e.g., 2.x to 3.x or 4.x) may include significant changes requiring migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zitadel Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53895 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data