External risk intelligence

Zipline WebAuthn Authentication Bypass via Passkey Login.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-126952

The vulnerability exists in a WebAuthn login endpoint, which is a public-facing authentication interface by design. WebAuthn is standard for identity verification on web applications, and services using this feature must expose the login endpoint to the internet to allow users to authenticate from any location.

Authentication Bypass

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory highlights a critical vulnerability in Zipline's WebAuthn login functionality that could allow unauthorized access to accounts, including administrative ones, by bypassing authentication through a compromised credential ID. The main concern is confirming relevance and exposure to affected systems.

  • Bypass authentication using a credential ID.
  • Administrative account access is at risk.
  • Confirm relevance and potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by first obtaining a user's passkey credential ID. With this ID, they can then bypass authentication on the WebAuthn login endpoint, allowing them to create a new session. This could grant them unauthorized access, potentially including administrative privileges if they target a SUPERADMIN account.

  • Requires obtaining a target's credential ID.
  • Triggers through a WebAuthn login bypass.
  • Risk of account impersonation and admin control.

Live Threat

Current exploitation, exposure, and threat context

The Zipline WebAuthn login endpoint could allow an attacker to bypass authentication. This is possible when an attacker obtains a target's registered credential ID, enabling them to create a session without the need for the target's authenticator. This could lead to unauthorized access to accounts, including those with administrative privileges.

  • Account access and administrative control.
  • Bypassing authentication using a credential ID.
  • Unauthorized administrative access to SUPERADMIN accounts.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Zipline application owner and platform team are likely responsible for addressing this authentication bypass vulnerability. The first practical move is to identify all Zipline instances, confirm their exposure and criticality, and then assign an accountable owner to plan remediation.

  • Application and platform teams own the issue.
  • Verify Zipline instances and their reachability.
  • Plan remediation based on confirmed 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 the Zipline software?

Zipline is an application that facilitates secure data sharing and file hosting. It includes various authentication mechanisms, such as WebAuthn for passkeys, to help users manage access to their uploaded files and account data.

What does CWE-347 mean for CVE-2026-126952?

CWE-347 refers to improper verification of cryptographic signatures. In this vulnerability, Zipline fails to properly validate the WebAuthn assertion during login. Instead of verifying the proof of possession from a physical authenticator, the system trusts the provided credential ID, allowing an attacker to log in as another user.

How does an attacker trigger this bypass?

To trigger the vulnerability, an attacker must first obtain a registered passkey credential ID belonging to a target user. Once they have this ID, they can submit it to the WebAuthn login endpoint. The system incorrectly initiates a session for that ID without requiring the actual authenticator device, effectively bypassing the security check.

Is my Zipline instance at risk?

According to Halo Surface Signal, this vulnerability is critical because the affected WebAuthn endpoint is designed to be public-facing to enable remote logins. If your instance is accessible via the internet, it is at higher risk of unauthorized access, as the login process is exposed by default.

What should I do first to secure my systems?

Begin by creating an inventory of all running Zipline instances to identify which ones are currently reachable. Verify the status and version of these instances, then engage your platform or application team to assign ownership for the remediation process once updates become available.

References