VulnSocial

CVE-2026-55672Disclosure

LOWCVSS 7.4 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's OAuth2 and OIDC CodeExchange, RefreshToken, and device token flows fail to verify that the requesting client matches the client that initiated the authorization flow, allowing intercepted grants or refresh tokens to be exchanged under a different client. This issue is fixed in versions 3.4.12 and 4.15.2.

Back to dashboard
0.0/ 10 priority

Sources & remediation

Other references
Weakness type (CWE)
CWE-287CWE-863

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-07-12: 1Technical Details · 2026-07-12: 107-12
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
Full discourse1 post
  • Cyber Threat Observatory | Alan Turing Institute@TuringCyberObs
    Disclosure

    CVE-2026-55672 ZITADEL Missing client ID binding could allow OAuth/OIDC tokens issued for one client to be used against another, weakening token-based access controls Full analysis: https://github.com/alan-turing-institute/cyber-threat-observatory/blob/main/reports/2026-07-10/TIER_2_CVE-2026-55672.md #CyberSecurity #IdentitySecurity #VulnerabilityManagement

    Post summary

    The post announces a ZITADEL vulnerability (CVE‑2026‑55672) where missing client‑ID binding permits cross‑client token reuse, potentially weakening token‑based access controls, and refers readers to a detailed GitHub analysis.

    00020174
    59 followersView on X

Explore more

Back to dashboard