CVE-2026-56768

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
30.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 30, 2026

Advisory Details (5)

Auto-updated Jun 25, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

Seahub < 13.0.23 - Authentication Bypass in ShareLinkZipTaskView GET Method | Advisories | VulnCheck

https://www.vulncheck.com/advisories/seahub-authentication-bypass-in-sharelinkziptaskview-get-method
generic

Seafile Wiki

https://plus.seafile.com/wiki/publish/seafile-wiki/v5D5/
generic

[Security] SHARE_LINK_LOGIN_REQUIRED bypass on GET /api/v2.1/share-link-zip-task/ · Issue #9050 · haiwen/seahub · GitHub

https://github.com/haiwen/seahub/issues/9050
github_commit

commit b609949cf64e (haiwen/seahub)

Fix landed in haiwen/seahub commit b609949cf64e — awaiting tagged release

https://github.com/haiwen/seahub/commit/b609949cf64ed6a15708d0fb5ea9c179962e23cc
github_commit

commit 162cddae0831 (haiwen/seahub)

Fix landed in haiwen/seahub commit 162cddae0831 — awaiting tagged release

https://github.com/haiwen/seahub/commit/162cddae0831188d02bb8d451dc2193e197dcc57

Vendor Advisories for CVE-2026-56768(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 59× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 19:12 UTCEG score recompute
  2. 2026-07-06 19:12 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 07:24 UTCEG score recompute
  6. 2026-07-06 07:24 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 19:35 UTCEG score recompute
  10. 2026-07-05 19:35 UTCGHSA enrichment
  11. 2026-07-05 07:46 UTCEG score recompute
  12. 2026-07-05 07:46 UTCGHSA enrichment
  13. 2026-07-04 19:56 UTCEG score recompute
  14. 2026-07-04 19:56 UTCGHSA enrichment
  15. 2026-07-04 08:08 UTCEG score recompute
  16. 2026-07-04 08:08 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 20:15 UTCEG score recompute
  20. 2026-07-03 20:15 UTCGHSA enrichment
  21. 2026-07-03 08:26 UTCEG score recompute
  22. 2026-07-03 08:26 UTCGHSA enrichment
  23. 2026-07-02 20:38 UTCEG score recompute
  24. 2026-07-02 20:38 UTCGHSA enrichment
  25. 2026-07-02 08:48 UTCEG score recompute
Show 34 more
  1. 2026-07-02 08:48 UTCGHSA enrichment
  2. 2026-07-01 20:56 UTCEG score recompute
  3. 2026-07-01 20:56 UTCGHSA enrichment
  4. 2026-07-01 15:07 UTCEPSS rescore
  5. 2026-07-01 09:07 UTCEG score recompute
  6. 2026-07-01 09:07 UTCGHSA enrichment
  7. 2026-06-30 23:22 UTCEPSS rescore
  8. 2026-06-30 21:18 UTCEG score recompute
  9. 2026-06-30 21:18 UTCGHSA enrichment
  10. 2026-06-30 09:29 UTCEG score recompute
  11. 2026-06-30 09:29 UTCGHSA enrichment
  12. 2026-06-29 21:41 UTCEG score recompute
  13. 2026-06-29 21:41 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 09:52 UTCEG score recompute
  16. 2026-06-29 09:52 UTCGHSA enrichment
  17. 2026-06-28 22:03 UTCEG score recompute
  18. 2026-06-28 22:03 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 10:14 UTCEG score recompute
  21. 2026-06-28 10:14 UTCGHSA enrichment
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-27 22:24 UTCEG score recompute
  25. 2026-06-27 22:24 UTCGHSA enrichment
  26. 2026-06-27 10:35 UTCEG score recompute
  27. 2026-06-27 10:35 UTCGHSA enrichment
  28. 2026-06-27 03:08 UTCEPSS rescore
  29. 2026-06-26 22:46 UTCEG score recompute
  30. 2026-06-26 22:46 UTCGHSA enrichment
  31. 2026-06-26 10:57 UTCEG score recompute
  32. 2026-06-26 10:57 UTCGHSA enrichment
  33. 2026-06-25 19:49 UTCEG score recompute
  34. 2026-06-25 19:49 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-56768?
CVE-2026-56768 is a high vulnerability published on June 25, 2026. Seahub before 13.0.23 does not enforce SHARELINKLOGIN_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…
When was CVE-2026-56768 disclosed?
CVE-2026-56768 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56768 actively exploited?
CVE-2026-56768 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56768?
CVE-2026-56768 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-56768?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56768, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56768

Explore →

Is Your Infrastructure Affected by CVE-2026-56768?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs