All vulnerabilities

Servers and applications

CVE-2026-55669

Missing Token Audience Validation (`aud`) in JWT IdP Provider

Severity
Medium 4.2
Published
17 Jun 2026
Last changed
17 Jun 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.4.12, 4.15.2
Exploit chance
0.2% in the next 30 daysHigher than 4% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Origin validation error (CWE-346)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read some data · Change some data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Also known as
GHSA-g5h5-m4hm-xjrr
Sources
Project advisories (GitHub)

Description

An authentication bypass vulnerability was discovered in ZITADEL's external JWT Identity Provider (IdP) implementation.

When validating JSON Web Tokens (JWTs) from an external provider, ZITADEL properly checks the token's cryptographic signature and issuer (iss), but it fails to validate the audience (aud) claim.

As a result, any validly signed token from the trusted issuer will be accepted. An attacker who is a legitimate user of a completely separate service sharing the same enterprise Identity Provider can intercept or present their token for that service to ZITADEL, successfully authenticating as that user without authorization.

In a controlled enterprise environment where Identity Providers are explicitly managed, the operational risk is localized. Exploitation requires that an attacker already possesses a valid standard user session token from a shared, trusted issuer intended for an entirely different relying party, limiting the vector to specific, rare cross-service setups…

From zitadel/zitadel's security advisory. Shortened; the full text is there.

Workarounds

The recommended solution is to update ZITADEL to a patched version.

If an immediate upgrade is not possible, you can mitigate the risk at the infrastructure layer:

  • At the IdP: Ensure the external Identity Provider issues scoped tokens with highly unique, non-overlapping audience values that cannot be misconstrued by separate service deployments.
  • At the Perimeter: Deploy a reverse proxy, API gateway, or Web Application Firewall (WAF) layer in front of ZITADEL to inspect incoming identity tokens and explicitly drop requests where the aud field does not strictly match ZITADEL's deployment…
Workarounds as given by zitadel/zitadel's security advisory.

Affected software

SoftwareAffected versions
ZITADELServers and applications · github:zitadel/zitadel
  • Every version before 3.4.12
  • From 4.0.0 before 4.15.2

About ZITADEL

ZITADEL - Identity infrastructure, simplified for you.

From its GitHub repository.
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

References