CyberSecBulletin
CVE-2025-31123NVD status: Analyzed

zitadel: Use of a Key Past its Expiration Date

CVE-2025-31123 is a high-severity use of a key past its expiration date vulnerability in zitadel, with a CVSS 3.1 base score of 8.7 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. Affected zitadel versions: >= 2.62.0, < 2.63.9; >= 2.64.0-rc.1, < 2.64.6; >= 2.65.0-rc.1, < 2.65.7, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.4% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of zitadel you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Zitadelzitadel>= 2.62.0, < 2.63.9; >= 2.64.0-rc.1, < 2.64.6; >= 2.65.0-rc.1, < 2.65.7; >= 2.66.0-rc.1, < 2.66.16; >= 2.67.0-rc.1, < 2.67.13; >= 2.68.0-rc.1, < 2.68.9; >= 2.69.0-rc.1, < 2.69.9; >= 2.70.0-rc.1, < 2.70.8; and 1 more rangesNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (github.com).

Official description

Zitadel is open-source identity infrastructure software. A vulnerability existed where expired keys can be used to retrieve tokens. Specifically, ZITADEL fails to properly check the expiration date of the JWT key when used for Authorization Grants. This allows an attacker with an expired key to obtain valid access tokens. This vulnerability does not affect the use of JWT Profile for OAuth 2.0 Client Authentication on the Token and Introspection endpoints, which correctly reject expired keys. This vulnerability is fixed in 2.71.6, 2.70.8, 2.69.9, 2.68.9, 2.67.13, 2.66.16, 2.65.7, 2.64.6, and 2.63.9.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of a Key Past its Expiration Date

The product uses a cryptographic key past its expiration date.

How developers prevent this class of flaw

  • Adequate consideration should be put into the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.
  • Replace keys within a period of time proportional to their strength.

More Use of a Key Past its Expiration Date vulnerabilities (CWE-324)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in zitadel

All zitadel vulnerabilities

Recent Use of a Key Past its Expiration Date vulnerabilities

Spotted an error? Tell us.