Synology still ships Docker Engine 24.0.2, five major versions behind upstream, and finally details DSM 7.4’s 25 CVEs
On 10 November 2026, Synology publishes advisory Synology-SA-26:18 — 25 CVEs in DSM, eight of them Important — and confirms Container Manager still runs Docker Engine 24.0.2, five major versions behind upstream. Patch DSM immediately, the only mitigation, and if you depend on a modern Docker engine, compare the alternatives.
5 November 2026. Synology publishes Container Manager 24.0.2-1707, an update whose release note contains a single fix. 24.0.2. The number of the Docker engine still bundled — the same one shipped in February 2025, five major versions behind upstream. 10 November 2026. The vendor finally details advisory Synology-SA-26:18: 25 CVEs in DSM, eight of them Important. Why it matters: the first half of the story says Synology won’t close its Docker gap, and the second says its NAS boxes are first-rank targets that must be patched immediately.
Container Manager 24.0.2-1707: an update, the same engine
The release note dated 5 November 2026 contains one fix: “Fixed an issue where the version of containerized services in Web Station might not be updated.” Nothing about the engine. And for good reason: Container Manager still bundles Docker Engine 24.0.2, an engine Docker itself published in May 2023.
Since February 2025, Synology has shipped seven Container Manager builds — 1535, 1542, 1543, 1606, 1630, 1706, and now 1707 — and in every one of them the only number that moves is the one at the end. Meanwhile upstream kept moving: Docker Engine 29.9.3 landed on 3 November 2026, and 29.10 is in release candidate. The gap is five major versions.
The contrast with the competition is stark. UGREEN ships Docker Engine 29.6.2 in UGOS Pro since August 2026; ASUSTOR offers the same engine in App Central, last updated 27 October 2026; TerraMaster moved its Container Manager to the Docker 29 branch in August and announced 29.7.1 for TOS 7 ARM on 3 November 2026. Even QNAP, rarely praised for velocity, is on 27.1.2. Synology is last, by a mile.
For a homelab, the lag is not cosmetic. Engine 24.0.2 lacks the security fixes, networking features, and optimisations of the 27, 28, and 29 branches — the very branches that closed image supply-chain holes in 29.8.2 and 29.9.3. A Synology running containers therefore runs on an engine whose holes are known, and fixed elsewhere, for months.
Synology-SA-26:18: what the “silent” update was hiding
On 12 October 2026, Synology released DSM 7.4.1-90080 Update 1 with a laconic changelog: “Fixed multiple security vulnerabilities.” No CVEs, no details. On 10 November 2026, advisory Synology-SA-26:18 finally lifts the veil: 25 CVEs in DSM, 8 Important and 17 Moderate. Affected products: DSM 7.4, fixed in 7.4.1-90080-1 or later, and DSM 7.3, fixed in 7.3.2-86009-5 or later. The Mitigation field contains a single word: None. The update is the only protection.
The three most serious, at CVSS 8.8, all let a remote authenticated user read or write arbitrary files, with denial of service on top. CVE-2026-13672 is an authorization bypass in SSOAuth; CVE-2026-18792, a path traversal in the Sharing API; CVE-2026-74857, a missing authentication step in the Auth API.
Three more sit at 8.1. CVE-2026-18596 bypasses OTP: an attacker who already holds valid credentials neutralises the very barrier meant to save them when the password has leaked. CVE-2026-81584 is an SQL injection in the User API, exploitable by whoever controls a compromised LDAP or Active Directory server. CVE-2026-19048, a link-resolution flaw in the thumbnail component, allows writing arbitrary files.
Two flaws complete the Important set. CVE-2026-18633 (7.5), an uninitialized pointer in nfsd, lets a remote attacker with no account crash the service. CVE-2026-75785 (7.2) is an OS command injection in the VPN API, reserved to administrator accounts. Among the Moderate ones: missing authentication in the WebDAV API (CVE-2026-15198), a faulty certificate check in the support form (CVE-2026-15201) — and, as an irony, an incorrect authorization in Security Advisor itself (CVE-2026-124993), the tool meant to protect the NAS.
What this means for a homelab
The common thread across these flaws is the exposure surface. A Synology box is often reachable from the internet through QuickConnect or a port forward, and it centralises files, backups, and containers. Eight Important flaws — three at 8.8 — on a device that exposed, with no mitigation other than the patch, is exactly the profile attackers automate within hours of an advisory going public.
The episode carries a double lesson. First, opacity is no excuse to wait: those who installed the 12 October update without knowing the CVEs were protected four weeks before the advisory was published. Second, the Docker lag and DSM security are the same symptom — a platform that keeps a 2023 engine is a platform whose discipline around third-party component updates has slipped, and it eventually shows up in the CVEs.
The verdict
If you run a Synology on DSM 7.4 or 7.3, update it today: 7.4.1-90080-1 and 7.3.2-86009-5 are the only protection, and the 8.8 flaws won’t wait. Also check that QuickConnect and exposed ports are not open wider than necessary.
If you depend on modern containers on your NAS, compare your options honestly: the 24.0.2 engine is a real drag on security and networking, and the competitors (UGREEN, TerraMaster, ASUSTOR) ship Docker 29. Staying on Synology is defensible — the ecosystem and the stability of DSM have real value — but it should be a knowing choice, made with the understanding that its Docker engine will, in all likelihood, keep lagging upstream.