Synced 17 Jun 2026 22:27 UTC Account
← Seafile

Seafile vulnerabilities: known CVEs & security history

Seafile · File sync & share · 6 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Seafile release lines — 6 in total. A CVE here doesn't mean your version is affected — check Seafile's current status and the safe version to run.

6
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Seafile CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2013-7469 high 7.5 1% 2019
CVE-2025-41080 medium 6.1 0% 2025
CVE-2025-41079 medium 6.1 0% 2025
CVE-2023-28874 medium 6.1 0% 2023
CVE-2023-28873 medium 5.4 0% 2023
CVE-2021-30146 medium 5.4 1% 2021

Is my Seafile version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Seafile version → · Monitor Seafile for new CVEs →

Seafile vulnerabilities — frequently asked

How many known vulnerabilities does Seafile have?

IsItPatched tracks 6 CVEs for Seafile. 0 are critical-severity and 1 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Seafile have any actively-exploited vulnerabilities?

None of Seafile's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Seafile vulnerability?

Among tracked issues, CVE-2013-7469 (HIGH, CVSS 7.5) ranks highest — a CWE-326 weakness.

Is Seafile safe to use?

It depends on the version. The latest supported Seafile release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Seafile security status · Seafile end-of-life · actively-exploited CVEs. Always verify against Seafile's advisories — see our disclaimer.