4.3

CVE-2026-27840: zitadel

CVSS: 4.3v3.1MediumAnalyzed
AliasesGHSA-6mq3-xmgp-pjm5GO-2026-4573
Published 26-02-2026Last modified 26-02-2026

Vulnerability summary

CVE-2026-27840 is a medium (CVSS 4.3) vulnerability in zitadel. EPSS estimates a 0.23% chance of exploitation in the next 30 days, higher than 12.9% of scored vulnerabilities.

Overall risk
17/100
0100
Low · default modelHow is this calculated?
CVSS score
4.3/10
010
Medium · v3.1 (CVE.org)
EPSS score
0.23%
0%100%
Low · +0.09 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 2 · Related 2

Timeline

  1. 26-02-2026
    PublishedVulnerability first disclosed.
  2. 26-02-2026
    Last modifiedVulnerability information updated.

Description

ZITADEL is an open source identity management platform. Starting in version 2.31.0 and prior to versions 3.4.7 and 4.11.0, opaque OIDC access tokens in the v2 format truncated to 80 characters are still considered valid. Zitadel uses a symmetric AES encryption for opaque tokens. The cleartext payload is a concatenation of a couple of identifiers, such as a token ID and user ID. Internally Zitadel has 2 different versions of token payloads. v1 tokens are no longer created, but are still verified as to not invalidate existing session after upgrade. The cleartext payload has a format of `<token_id>:<user_id>`. v2 tokens distinguished further where the `token_id` is of the format `v2_<oidc_session_id>-at_<access_token_id>`. V1 token authZ/N session data is retrieved from the database using the (simple) `token_id` value and `user_id` value. The `user_id` (called `subject` in some parts of our code) was used as being the trusted user ID. V2 token authZ/N session data is retrieved from the database using the `oidc_session_id` and `access_token_id` and in this case the `user_id` from the token is ignored and taken from the session data in the database. By truncating the token to 80 chars, the user_id is now missing from the cleartext of the v2 token. The back-end still accepts this for above reasons. This issue is not considered exploitable, but may look awkward when reproduced. The patch in versions 4.11.0 and 3.4.7 resolves the issue by verifying the `user_id` from the token against the session data from the database. No known workarounds are available.

CVSS metrics

3 scores · 3 sources · 1 version

EPSS trend

Probability

0.23%

Chance of exploitation in the next 30 days

Percentile

13%

Versus all other CVEs

30-day change

+0.09 pp

From 0.14% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.23%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Github.com/zitadel1 product
  • zitadel≥ 4.0.0, < 4.11.0 | ≥ 3.0.0, < 3.4.7 | ≥ 2.31.0, ≤ 2.71.19 | All versions (No fix recorded) | < 1.80.0-v2.20.0.20260216092519-feab8e1fa371
Zitadel1 product
  • zitadel≥ 2.31.0, ≤ 2.71.19 | ≥ 3.0.0, < 3.4.7 | ≥ 4.0.0, < 4.11.0

2 vendors · 2 products

References

7 links