Servers and applications
CVE-2026-27840
Truncated opaque tokens are still valid
- Severity
- Medium 4.3
- Published
- 25 Feb 2026
- Last changed
- 17 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.4.7, 4.11.0
- Exploit chance
- 0.2% in the next 30 daysHigher than 5% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-302
- Attack
- Over the network · No login needed · Needs someone to click or open something
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N- Also known as
- GHSA-6mq3-xmgp-pjm5
- Sources
- NVD, Project advisories (GitHub)
Description
Opaque OIDC access tokens in 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 :. v2 tokens distinguished further where the token_id is of the format v2_-at_. This is an example of such a cleartext: V2_354201447279099906-at_354201447279165442:354201364702363650
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.
Workarounds
The recommended solution is to update ZITADEL to a patched version.
Affected software
| Software | Affected versions |
|---|---|
ZITADELServers and applications · cpe:a:zitadel:zitadel |
|
ZITADELServers and applications · github:zitadel/zitadel |
|
About ZITADEL
ZITADEL - Identity infrastructure, simplified for you.
- GitHub stars
- 15,585GitHub, 15 Nov 2026
- Forks
- 1,432GitHub, 15 Nov 2026
- Latest release
- v4.20.3GitHub, 15 Nov 2026
- Released
- 13 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 16 Mar 2020GitHub
Vulnerabilities in ZITADEL
- In our list
- 103
- Published in the last 12 months
- 72
- Critical, last 12 months
- 13
- High, last 12 months
- 37
- Known exploited
- 0
- GHSA-qqv8-37gw-ww2qMissing second-factor check on authenticator enrollment in Login V2 (MFA bypass)High 8.1 18 Nov 2026
- GHSA-vg5j-vf6h-586mLogin V2 exposes internal functions as unauthenticated endpointsHigh 7.4 13 Nov 2026
- GHSA-3gwf-ph53-v73cLogin V2: authentication bypass via unauthenticated (zero-factor) session for OIDC and SAML requestsHigh 7.4 13 Nov 2026
- GHSA-gx82-3gqq-j4h5Session API and Login V2: organization login policy not enforced for password sign-inHigh 7.1 13 Nov 2026
- GHSA-fphg-99ff-7qrpLogin V2: external IdP sign-in callback not bound to the initiating browser (login CSRF / session swapping)Medium 5.4 13 Nov 2026
- GHSA-pm3x-9hh8-g745Login V2: Arbitrary Redirect URL AcceptedMedium 4.3 13 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-27840
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-27840
- GitHub Advisory Database https://github.com/advisories/GHSA-6mq3-xmgp-pjm5
- github.com https://github.com/zitadel/zitadel/security/advisories/GHSA-6mq3-xmgp-pjm5