# CVE-2026-56768: Seahub < 13.0.23 - Authentication Bypass in ShareLinkZipTaskView GET Method

> Unauthenticated attackers with a share-link token can bypass authentication to download entire shared directory trees via the share-link-zip-task endpoint.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-w52g-25r7-3c46

## What is CVE-2026-56768?

CVE-2026-56768 is a high-severity missing authorization vulnerability in haiwen seahub, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Seahub before 13.0.23 does not enforce SHARE_LINK_LOGIN_REQUIRED on GET /api/v2.1/share-link-zip-task/, allowing unauthenticated users to bypass authentication. Attackers with a folder share-link token can call the GET endpoint to obtain a fileserver zip token and download entire shared directory trees.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-56768?


## How do I fix CVE-2026-56768?

No fix has been published for CVE-2026-56768 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56768 being exploited?

There is no known exploitation of CVE-2026-56768 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56768 and fix it if it is affected.

What it is: CVE-2026-56768 is a high-severity missing authorization vulnerability in haiwen seahub, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56768 in the wild and no public exploit code.

Affected product: haiwen seahub. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56768/ (Markdown: https://insights.sbomify.com/CVE-2026-56768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56768
- OSV: https://osv.dev/vulnerability/CVE-2026-56768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56768/
Summaries are generated and may contain mistakes; the official description above is the record.