VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

syncthing: vulnerability history, versions and safety

syncthing is a package in the Debian ecosystem. Vulert records 5 vulnerabilities for it across 21 releases, from Jan 2018 to Jun 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded U5
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all syncthing vulnerabilities

Vulert verdict on syncthing i

Updated on 23 Oct 2026

Careful: one of the 5 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 5 vulnerabilities on record across 5 years, none in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 5 over 5 years · 0 in the last year i
  • Latest disclosure 06 Jun 2023 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for syncthing, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 21 of 21 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2
  • 2021 2
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for syncthing

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Symlink Traversal Vulnerability in Syncthing: Arbitrary File Overwrite Risk 7.5 high 0.14.36+ds1-1 02 Jan 2018
Critical Crash Vulnerability in Syncthing Relay Server 7.5 high 1.12.1~ds1-3 06 Apr 2021
Stored Cross-Site Scripting Vulnerability in Syncthing 5.4 medium No fix published 06 Jun 2023
Symlink Traversal Vulnerability in Syncthing: Arbitrary File Overwrite Risk N/A unrated 0.14.36+ds1-1 02 Jan 2018
Critical Crash Vulnerability in Syncthing: Relay Server Exploit N/A unrated 1.12.1~ds1-3 06 Apr 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About syncthing

Is syncthing safe to use?

Vulert records 5 vulnerabilities for syncthing in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does syncthing have?

5 vulnerabilities are recorded for syncthing in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 5 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new syncthing vulnerabilities disclosed?

0 vulnerabilities were recorded for syncthing in the last 12 months, and the oldest entry in this database dates to 02 Jan 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of syncthing are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor syncthing for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the syncthing version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.