External risk intelligence

Zulip Server OpenID Connect Email Verification Bypass Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-102893

Zulip is commonly deployed as an internet-facing team collaboration and communication platform. As a web-based application providing remote access to organizational messaging, it typically presents an external web interface to facilitate communication among distributed users. The authentication surface exposed for identity provider integration is a standard, internet-reachable component of such deployments.

Authentication Bypass

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security issue has been identified in Zulip, an open-source team collaboration tool, where an authentication flaw could allow unauthorized access to existing accounts under specific misconfiguration scenarios. This vulnerability requires a compromised or misconfigured identity provider to exploit, and is addressed in the latest version. The main concern is confirming relevance and exposure.

  • Uncontrolled login to accounts via email.
  • Protects against unauthorized account access.
  • Confirm exposure and relevance to our operations.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by leveraging a misconfigured identity provider that falsely claims a user's email is verified. Zulip, a team collaboration tool, would incorrectly associate this unverified email with an existing account, allowing the attacker to gain access to that account without controlling the associated email address. This could lead to unauthorized access and compromise of sensitive communications within the platform.

  • Requires misconfigured trusted identity provider.
  • Triggered by matching unverified email claims.
  • Risk of unauthorized account access.

Live Threat

Current exploitation, exposure, and threat context

When a Zulip server is misconfigured with an identity provider that returns an unverified email address, an attacker could potentially log into an existing account associated with that email. This scenario requires a specific setup where the identity provider does not properly verify email ownership during authentication.

  • User accounts could be compromised.
  • Authentication bypass via misconfigured IdP.
  • Unauthorized access to team communications.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Zulip, an open-source team collaboration tool, and requires a misconfigured identity provider for exploitation. Real-world ownership likely falls to application or platform teams managing Zulip, with support from network and security teams for exposure review. The initial practical step is to identify Zulip deployments, determine their exposure, and confirm if the identity provider is misconfigured.

  • Application owners should confirm identity provider configuration.
  • Verify if identity provider is misconfigured.
  • Plan remediation based on exposure risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Zulip and how is it used?

Zulip is an open-source team collaboration platform designed to streamline communication through threaded conversations. Organizations use it to centralize messaging, organize discussions by topic, and integrate with various external services, including third-party identity providers for user authentication.

What does CWE-287 mean in the context of CVE-2026-102893?

CWE-287 refers to improper authentication. In this CVE, the software fails to properly validate the 'email_verified' claim during the OpenID Connect process. This means the system trusts an unverified email address provided by an external source as proof of identity, allowing an authentication bypass if that source is misconfigured.

How can an attacker trigger this Zulip vulnerability?

An attacker triggers this by using a misconfigured identity provider that sends an unverified email address to Zulip. If the provider asserts an email that belongs to an existing user without confirming the user actually owns that email, Zulip grants access to that account. Deployments using identity providers that strictly ensure only verified emails are sent remain unaffected.

Is my Zulip instance likely at risk according to Halo Surface Signal?

Halo Surface Signal identifies Zulip as a platform frequently deployed as an internet-facing service to support distributed teams. Because this interface is reachable externally to facilitate remote collaboration, the authentication endpoints involved in this vulnerability are often exposed, making it important to verify your specific configuration.

What are the first steps to secure my Zulip deployment?

Begin by confirming the version of Zulip you are running. Since this issue is resolved in version 12.2, updating is the primary path to security. Simultaneously, coordinate with your team to review the configuration of your trusted identity providers to ensure they are not incorrectly emitting unverified email claims that could lead to account compromise.

References