Introduction
An attacker who can reach the rsync service on an unpatched Synology NAS may be able to write arbitrary files to the device, read specific files, and degrade availability, all without supplying credentials. Because rsync is the channel many organizations use for backups and replication, this flaw sits directly on the path that is supposed to protect data integrity on these appliances.
DiskStation Manager (DSM) is the operating system that runs Synology's NAS and storage appliances. Synology, founded in 2000, reports more than 13 million installations and tens of thousands of channel partners, and its account of the IT Markt Report 2024 states that 19% of respondents among more than 13,000 large Swiss companies deployed Synology NAS or SAN systems. Those figures describe the vendor footprint, not the number of devices exposed to CVE-2026-85101, which depends entirely on the installed DSM build.
Technical Information
At a glance
- Vendor: Synology Inc. (the CVE feed lists the vendor as "Unknown", but the vendor advisory and the CVSS assessor both identify Synology)
- Component: rsync in DSM
- Weakness: CWE-288, Authentication Bypass Using an Alternate Path or Channel
- CVSS 3.1: 8.6,
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L - Vendor severity: Important for this CVE; the combined advisory Synology_SA_26_19 is rated Critical because it also covers CVE-2026-76954, a separate CVSS 9.8 SQL injection in the DSM Auth API
- Disclosure: Synology's advisory was published November 10, 2026 at 17:06:42 UTC+8. The NVD publication date in the CVE data is November 12, 2026. These are separate publication events, not conflicting dates.
Root cause
MITRE defines CWE-288 as a product that requires authentication but exposes another path or channel to the same resources that does not enforce that requirement. In this case the alternate channel is DSM's rsync component. Synology states that before the fixed builds, a remote attacker could use it to read specific files, write arbitrary files, and conduct limited denial-of-service attacks.
That is the full extent of the confirmed root cause. DSM is closed source, and Synology has not released a commit, diff, or technical write-up. The advisory does not identify:
- the vulnerable binary, module, function, or request parameter
- the packet sequence or the comparison between the authenticated and alternate paths
- which files are readable, which locations are writable, or with what operating system privileges
- the exact denial of service behavior
- a required rsync configuration, a required port, or a list of affected hardware models
The advisory also does not establish remote code execution. These details cannot be reliably reconstructed from the CWE classification alone, so we do not speculate about them here.
Reading the CVSS vector
Using the FIRST CVSS v3.1 definitions:
- AV:N (Network): exploitable over the network. FIRST notes Network applies even when the attacker must be on the same intranet. It is not evidence that every NAS is exposed to the internet.
- AC:L (Low): no specialized access conditions or extenuating circumstances.
- PR:N (None): no privileges or credentials required.
- UI:N (None): no user interaction required.
- S:U (Unchanged): impact stays within the vulnerable component's security scope.
- C:L (Low): some loss of confidentiality; the attacker does not control what information is obtained, or the loss is limited. This matches "read specific files".
- I:H (High): total loss of integrity, matching "write arbitrary files".
- A:L (Low): reduced performance or intermittent availability without serious direct consequence, matching "limited denial of service".
The integrity impact is the center of gravity here. The score reflects intrinsic severity. Actual risk depends on whether rsync is enabled and who can reach it.
Attack flow, based on public information
- The attacker identifies a DSM device running a build below the fixed threshold for its branch, with the rsync service reachable from the attacker's network position.
- The attacker connects to the rsync service and uses the alternate path that does not enforce the authentication applied on DSM's primary access path. No credentials and no user interaction are needed.
- Through that channel the attacker can read specific files, write arbitrary files, or trigger limited denial of service.
- Arbitrary file write on a Linux appliance is commonly turned into persistence (for example cron entries, accounts, or SSH keys). This step is a general post-exploitation pattern used in our detection guidance below, not a documented chain for this CVE.
Exploitation status
The reviewed sources do not establish active exploitation. OffSeq's Threat Radar reports no public Nuclei template, no Metasploit or Exploit Database entry, no CISA KEV listing, and no attack traffic on its honeypot sensors. SecurityOnline and Daily Security Review also report no known exploitation and no public exploit. No threat actor is associated with this CVE. The advisory credits researchers from Viettel Cyber Security Research Lab and Aytio but does not map acknowledgments to individual CVEs.
Synology's October 29, 2026 statement about ransomware against outdated DSM versions concerns a different vulnerability patched in December 2024 (Synology SA 24:20). It does not mention CVE-2026-85101, and those attacks should not be attributed to this rsync flaw.
Patch Information
The only fix evidence is Synology's advisory Synology_SA_26_19, which marks the issue Resolved. The fix ships inside a normal DSM update, not as a separate rsync package. Minimum fixed builds per branch:
- DSM 7.4: 7.4.1-90080-1
- DSM 7.3: 7.3.2-86009-5
- DSM 7.2.2: 7.2.2-72806-10
- DSM 7.2.1: 7.2.1-69057-13
Synology build strings follow the pattern version, build, update. For example, 7.4.1-90080-1 means DSM 7.4.1, build 90080, Update 1. Synology fixed each branch separately, so administrators can patch without moving to a newer major release, a point Daily Security Review also makes. HKCERT's bulletin lists the same thresholds as "prior to" vulnerable cutoffs. DSM 7.1 and older do not appear in the fixed release table.
One update, two CVEs (and more). The same builds fix CVE-2026-76954, the CVSS 9.8 SQL injection in DSM's Auth API. Daily Security Review reports that the update cycle fixed 27 DSM flaws in total, and HKCERT links SA 26:19 with SA 26:18.
What the fix likely changes (inference, not confirmed by Synology). Given the CWE-288 classification, the fix probably routes rsync connections through the same authentication checks as DSM's primary login, closing the alternate path. Synology has not said which binary, module, or configuration changed.
When the fix actually shipped. Tweakers reports that the fixed builds were on Synology's download archive several weeks before the advisory. This is consistent with reports that the fixes were part of the October updates, and one Tweakers commenter says their NAS had the patched build installed on October 23. Devices that installed these builds automatically before November 10 may already be protected, but verify the installed version (Control Panel → Info Center) rather than assuming.
No workaround. The advisory's workaround field reads None. It does not offer a firewall rule, service setting, or credential change as a substitute for the update. MITRE's CWE-288 guidance (funnel access through a single choke point and check permissions on every resource access) is developer architecture guidance, not a deployable DSM mitigation.
Applying the update. CERT.LV recommends identifying all Synology storage systems, checking their software versions, and installing the vendor fixes urgently. Synology's documented workflow:
- In Synology Download Center, select the product type and model, then obtain the DSM update from the Operating System tab. Available updates can vary because DSM checks compatibility against the system configuration.
- For a manual update, download the
.patfile, open Control Panel > Update & Restore > Update, choose the manual update option, browse to the file, and click OK. The file does not need to be extracted or executed on the administrator's computer. - The system restarts automatically after the update, so schedule it for a quiet period.
NVD status. When the patch sources were compiled, an NVD lookup for CVE-2026-85101 returned "CVE ID Not Found", so NVD could not be used to confirm fixed versions. Synology's advisory is the authoritative source for patch thresholds.
Detection Methods
Synology's advisory provides affected builds but no root-cause detail, log artifacts, or indicators of compromise. There is no vendor or community Snort, Suricata, Sigma, or YARA signature for this bug, and nothing that identifies its traffic on the wire. Realistic detection therefore means (1) finding vulnerable builds and (2) hunting for the after effects implied by the impact statement.
1. Find exposure by DSM build number
This is the most reliable check. Treat any device below the following builds as vulnerable: 7.4.1-90080-1 (7.4), 7.3.2-86009-5 (7.3), 7.2.2-72806-10 (7.2.2), and 7.2.1-69057-13 (7.2.1).
The open-source akari-sora/synology-nas-cli project has two pieces of logic worth carrying into your own scanners:
- Check each advisory separately. A build can include fixes from earlier advisories (such as SA 26:13) and still lack SA 26:19. The tool's
nas status,nas doctor,nas incident, andnas alertcommands report the advisories separately, and a device counts as patched only if both are covered. - Do not treat unlisted branches as safe. Plain DSM 7.2 and DSM 7.1 or older are not listed in SA 26:19 and have no fix on that branch. A newer branch the advisory does not name is reported as
unknown, not patched.
The same document recommends confirming the installed build on the device by checking the smallfixnumber value in /etc.defaults/VERSION rather than trusting the GUI. Older branches can show "up to date" in Control Panel because DSM's auto-update does not move across major or minor branches.
2. Baseline the rsync channel
Daily Security Review notes rsync is widely used for backups and file sync on NAS devices, so alerting on all rsync traffic is not practical. On devices with rsync enabled:
- Inventory legitimate rsync peers (backup servers, replication partners).
- Alert on rsync sessions from any other source, especially internet-routable addresses.
- Treat transfers that write to the NAS from a peer that should only read (or the reverse) as suspicious.
This is behavioral hunting derived from the advisory, not a published signature.
3. Hunt for unexpected file writes and persistence
With integrity impact rated High, unexpected file changes are the most useful post-exploitation signal. The akari-sora incident guide includes root-level checks it wrote for a different campaign (C3RB3R ransomware exploiting CVE-2024-10441). It labels the account, SSH key, and cron checks as generic persistence checks, which makes them reasonable sweeps here too:
# Unexpected cron entries (also review /etc/crontab and /var/spool/cron) ls -la /etc/cron.d # Rogue accounts: a second uid 0 account or unknown users with uid >= 1024 awk -F: '$3>=1024 || ($3==0 && $1!="root")' /etc/passwd # Planted SSH keys ls -la /root/.ssh /var/services/homes/*/.ssh # Executables running from outside Synology paths or from temporary folders ls -l /proc/*/exe
The tool's nas incident --deep --json mode automates these checks, flagging cron lines outside Synology paths, accounts not on the allow list, executables outside Synology paths, and any authorized_keys file as WARN for review.
Do not copy that document's campaign-specific indicators (the 46.8.78.122 address, /etc/cron.d/synot*, /bin/libgld, .L0CK3D files) into CVE-2026-85101 rules. They belong to a different vulnerability and would create false confidence.
4. Watch for the limited denial of service
With availability impact rated Low, exploitation attempts may surface as rsync service instability: unexplained crashes, restarts, or failed backup and replication jobs. Correlate these with rsync connections from unknown sources and with the file integrity checks above.
If a public PoC or technical write-up appears, check Snort, Suricata, and Nuclei feeds again, since that would make network- and scanner-based detection possible.
Affected Systems and Versions
Synology DSM with the rsync component, in the following ranges:
- DSM 7.4: builds before 7.4.1-90080-1
- DSM 7.3: builds before 7.3.2-86009-5
- DSM 7.2.2: builds before 7.2.2-72806-10
- DSM 7.2.1: builds before 7.2.1-69057-13
Plain DSM 7.2, DSM 7.1, and older branches are not in the fixed release table. They are not listed in Synology_SA_26_19, and no fix is published on those branches. The briefing's NVD data records the status of configurations before DSM 7.2.1 as unknown, not confirmed unaffected. Treat these as unresolved rather than safe.
The public sources do not establish a required rsync configuration, a specific port, or a list of affected hardware models.
Vendor Security History
- SynoLocker (2014): Synology's August 7, 2014 advisory confirmed ransomware targeting older DSM releases through two vulnerabilities already fixed in November and December 2013. The lesson is the gap between published and installed fixes. It has no connection to the current rsync issue.
- October 2026 ransomware statement: On October 29, 2026, Synology said threat actors were exploiting a vulnerability patched in December 2024 against outdated DSM versions to encrypt data and extort ransom, directed users to Synology SA 24:20, and recommended automatic updates. This is separate from CVE-2026-85101.
- Companion flaw: CVE-2026-76954, a CVSS 9.8 SQL injection in the DSM Auth API, is covered by the same advisory and update matrix. Its mechanism and impact wording do not transfer to the rsync CVE.
- Response process: Synology's PSIRT handles receipt, investigation, coordination, and public reporting, with engineering and quality control involvement, fix testing, possible researcher verification, a Security Bug Bounty Program, and a stated 90-day disclosure timeline. These are policy commitments. For this CVE the observable response is a published advisory, four fixed builds, and a Resolved status.
References
- NVD: CVE-2026-85101
- Synology Security Advisory Synology_SA_26_19 (en global)
- Synology Security Advisory Synology_SA_26_19 (en us)
- HKCERT: Synology Products Multiple Vulnerabilities
- CERT.LV: Kritiskas Synology DSM ievainojamības (CVE-2026-76954, CVE-2026-85101)
- Daily Security Review: Synology patches 27 DSM flaws including CVSS 9.8 SQL injection
- Tweakers: Synology waarschuwt voor lekken die hackers toegang geven tot bestanden op NAS
- OffSeq Threat Radar: CVE-2026-85101
- SecurityOnline: Synology DiskStation Manager CVE-2026-76954 patched
- akari-sora/synology-nas-cli: INCIDENT C3RB3R guide
- MITRE CWE-288: Authentication Bypass Using an Alternate Path or Channel
- FIRST CVSS v3.1 Specification Document
- Synology: SynoLocker advisory
- Synology: Users urged to update DSM following ransomware attacks on outdated versions
- Synology Vulnerability Response Policy
- Synology Knowledge Center: How do I manually update the system?
- Synology Knowledge Center: DSM Update
- Synology Knowledge Center: What should I do before updating?
- Synology: About Us
- Synology: Named Leading Brand in Swiss Storage Market
- The Hacker News: Synology NAS devices targeted in ransomware attacks exploiting patched DSM flaw
- BeyondMachines: Ransomware targets Synology NAS devices



