Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Syncthing / v2.1.7

Syncthing v2.1.7

SAFE

No breaking/security/wait signals detected in release notes heuristics.

Published: 2026-10-21T06:10:26Z · GitHub release

Summary of changes

## What's Changed Built with Go 1.27.3. ## Fixes - fix: handle missing max-sequence file entries by @calmh in #10912 - fix(sqlite): avoid early garbage collection of deleted recv-enc files by @calmh in #10916 - fix(sqlite): do not generate unbounded prepared statements (ref #10913) by @calmh in #10915 - fix(discover): skip unnecessary identical global announce updates; obey retry-after by @calmh in #10918 - fix(protocol): convert panics on bad data to protocol errors by @calmh in #10923 - fix(model): verify local change before applying metadata shortcut (fixes #10924) by @calmh in #10925 - fix(model): ensure parent ownership is copied properly (fixes #8399) by @calmh in #10926 - fix(model): properly compare blocks when reconciling receive-only (fixes #10928) by @calmh in #10929 ## Other - build(deps): update dependencies by @calmh in #10917 …

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

14

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.