Skip to main content
Menu
CVEs

CVE

Zipline authentication bypass in WebAuthn passkey login

Affects Zipline through 4.4.0 when passkey authentication is enabled, with v4.4.0 as the reviewed affected release. No fixed version is listed in the checked facts.

CVE-2026-126952EUVD-2026-125113GHSA-6RW4-H2XG-JVVPGHSA-8G3F-425R-35RQ

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

9.2CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
See vendor advisory
Who is exposed
Not reported

Do first: Workaround: The checked facts name no workaround. The only stated condition is that passkey authentication is enabled, so the feature's status is the factor to review while no fix is listed.

Published
Last modified
Reference
Last checked
0.29% · 21st percentile
47/100
Unclear
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: poc
  • Automatable: no
  • Technical impact: total

Summary

Zipline, a file-sharing and upload server, has an authentication bypass in its WebAuthn (passkey) login endpoint. Remotely and without logging in, an attacker who knows a target's registered passkey credential ID can create a session for that account without its authenticator, potentially gaining administrative control of SUPERADMIN accounts.

Original description

Zipline through 4.4.0 contains an authentication bypass vulnerability in the WebAuthn login endpoint that creates sessions for a supplied registered credential ID without verifying the assertion. Attackers who obtain a target's passkey credential ID can impersonate that account without its authenticator, potentially gaining administrative control over SUPERADMIN accounts.

Who should check

Teams running Zipline 4.4.0 or earlier with passkey login enabled, including self-hosted instances with SUPERADMIN accounts.

“In v4.4.0, when passkeys are enabled, the WebAuthn login endpoint”

github.com

cve.now Index

47cve.now Index 47 of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.2, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 77 if added to CISA KEV
  • Would score about 72 if CISA's SSVC rates exploitation active
  • Would score about 52 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts name no workaround. The only stated condition is that passkey authentication is enabled, so the feature's status is the factor to review while no fix is listed.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126952 (Zipline through 4.4.0 WebAuthn Authentication Bypass via Passkey Login), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126952 (entry last updated 2026-11-13):
Affected:
- diced zipline: through 4.4.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Passkey authentication is enabled (source: https://github.com/diced/zipline/security/advisories/GHSA-8g3f-425r-35rq)
- Zipline v4.4.0 is the affected release (source: https://github.com/diced/zipline/security/advisories/GHSA-8g3f-425r-35rq)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126952 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126952 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diced/zipline/security/advisories/GHSA-8g3f-425r-35rq
- https://www.vulncheck.com/advisories/zipline-through-4.4.0-webauthn-authentication-bypass-via-passkey-login
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126952
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126952"}.

Public exploit activity

100%0Posted on X by cve.nowNov 13Nov 17
  • EPSS: 0.29%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Affected versions

  • diced zipline

    through 4.4.0

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126952

Is CVE-2026-126952 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An attacker who obtains a target's registered passkey credential ID can log in as that account without its authenticator. If the account is a SUPERADMIN, this may give administrative control.Source: github.com

Which versions are affected by CVE-2026-126952?

zipline: through 4.4.0.Source: cve.now feed data

Am I affected, and how do I check?

The checked facts list Zipline from the first release through 4.4.0, and the reviewed affected release is v4.4.0. The issue applies when passkeys are enabled and the WebAuthn login endpoint is in use, so check whether passkey login is enabled on the instance.Source: github.com

How do I fix CVE-2026-126952?

The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given from them. Check the vendor's advisory for newer patch information.Source: github.com

What if there's no patch?

The checked facts name no workaround. The only stated condition is that passkey authentication is enabled, so the feature's status is the factor to review while no fix is listed.Source: github.com