Automated Threat Modeling

Overview of CVE-2026-76954: Unauthenticated SQL Injection in the Synology DSM Auth API

A brief summary of CVE-2026-76954, a critical CWE-89 SQL injection in the Synology DiskStation Manager Auth API that lets unauthenticated remote attackers read or write arbitrary files and cause denial of service. Covers affected DSM builds, the fixed releases and how the fix was shipped.

CVE Analysis

9 min read

Gaurav Sarraf
Gaurav Sarraf

2026-11-11

Overview of CVE-2026-76954: Unauthenticated SQL Injection in the Synology DSM Auth API

Introduction

A SQL injection flaw in the authentication interface of Synology DiskStation Manager (DSM) lets a remote attacker with no credentials read or write arbitrary files on the NAS and cause denial of service. DSM runs storage, backup and collaboration workloads for a very large installed base. A flaw that is reachable before login, in the component that handles authentication, is a priority for anyone running these devices.

The NVD record lists the vendor as Unknown, but the product is Synology DSM. Synology rates the issue Critical with a CVSS 3.1 score of 9.8. Fixed builds exist for four DSM branches. As of November 12, 2026, the reporting we reviewed does not confirm exploitation in the wild.

Technical information

Root cause

CVE-2026-76954 is classified as CWE-89: Improper Neutralization of Special Elements used in an SQL Command, and it sits in the DSM Auth API. MITRE describes this weakness class as building SQL commands from externally influenced input without correctly neutralizing special elements, so attacker input can be interpreted as SQL syntax instead of plain data. That definition explains the bug class only. It does not reconstruct this particular exploit.

Synology's advisory states the confirmed consequences: remote attackers can read arbitrary files, write arbitrary files and conduct denial-of-service attacks.

DSM is closed source. Synology has not published a commit, a diff or any explanation at the code level, and the fix ships only as compiled firmware. For that reason, this post contains no vulnerable code snippet.

Severity vector

Synology, acting as the CVE Numbering Authority, published this vector:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

In practical terms:

  • The attack works over the network.
  • Attack complexity is low.
  • No privileges or user interaction are needed.
  • Scope is unchanged.
  • Impact on confidentiality, integrity and availability is high.

At the time of the source review, NVD had not added its own NIST assessment, so the 9.8 score comes from Synology. Under FIRST's CVSS framework, the Base score describes properties of the vulnerability itself. A 9.8 Base score is not evidence that the flaw is being exploited.

Attack flow, as far as the sources describe it

The public sources support only a high-level sequence:

  1. The attacker reaches the DSM Auth API over the network. The vector requires no account and no action from a user.
  2. The attacker sends input containing SQL special elements to the Auth API. The Auth API places that input into a SQL command without correctly neutralizing it.
  3. The database treats part of the attacker's input as SQL.
  4. According to Synology, the attacker can then read arbitrary files, write arbitrary files or cause denial of service.

Several details remain unpublished: the vulnerable request path, the parameter, the payload and the chain from SQL injection to file access. We have not filled these gaps with guesses.

The remote code execution question

Viettel Cyber Security Research Lab's advisory credits Nguyen Ba Nam Dung and describes the issue as a preauthentication, zero-click remote code execution. Synology's official impact statement is narrower: arbitrary file read and write, plus denial of service.

No public execution chain or proof of concept backs up the researcher's description. Treat remote code execution as the researcher's claim, not as a demonstrated outcome.

Disclosure timeline

  • Early October 2026: fixed builds appear in Synology's download archive (details in the Patch information section below).
  • November 10, 2026, 17:06:42 UTC+8: Synology publishes advisory Synology_SA_26_19.
  • November 12, 2026, 03:41:52 UTC: the CVE record is published, and NVD lists the same date.

These dates mark separate disclosure events, so they do not conflict.

Exploitation status

  • Exploitation in the wild: StackFlag's page, published November 12, 2026, lists the vulnerability as not known to be exploited. SecurityOnline reports that active attacks and public exploit code are not confirmed.
  • Exploit or detection material: the Viettel advisory provides no payload, detection signature or indicators.
  • CISA KEV: the catalog snapshot we reviewed is dated November 10, 2026 and contains 1,779 entries, and this CVE is not among them. That snapshot is older than the NVD publication, so it cannot tell us whether the CVE has been added since.
  • Attribution: no threat actor is linked to this CVE in the reviewed reporting.

None of this proves the flaw has not been exploited. It only describes what the public evidence currently shows.

Patch information

Synology fixed CVE-2026-76954 in advisory Synology_SA_26_19, published November 10, 2026. The advisory is rated Critical and its status is Resolved.

Fixed builds by branch

Synology backported the fix to each DSM branch it maintains. You can stay on your current branch and move to its patched build:

  • DSM 7.4: 7.4.1-90080-1 or later
  • DSM 7.3: 7.3.2-86009-5 or later
  • DSM 7.2.2: 7.2.2-72806-10 or later
  • DSM 7.2.1: 7.2.1-69057-13 or later

Reading the build string

The build string has three parts:

7.3.2 86009 5 version build update level

A device is patched only if it runs the listed update level or a higher one. For example, 7.3.2-86009 Update 4 is still vulnerable, and Update 5 is fixed. The major and minor version label alone does not tell you whether a device is protected. Always compare the full build identifier.

What the fix covers

The advisory classifies the flaw as CWE-89 in the Auth API, with the CVSS vector shown above. The same advisory also fixes CVE-2026-85101, an authentication bypass in rsync, and both fixes ship in the same builds.

Synology states there is no mitigation for either flaw. Installing the update is the only fix the vendor offers. HKCERT likewise recommends applying the vendor fixes.

What the code change probably looks like (not confirmed)

Without a diff, the exact change cannot be verified. The standard fix for CWE-89 in a login path is to stop placing request fields directly into SQL text. The usual techniques are parameterized or prepared statements, or strict validation of input against expected values. Synology has not confirmed which approach it used.

The fix shipped weeks before the advisory

The fixed builds were available in Synology's download archive about a month before the advisory was published:

  • The 7.2.1-69057-13 packages are dated September 30 to October 1, 2026.
  • The 7.3.2-86009-5 packages are dated October 2, 2026.
  • The 7.4.1-90080 Update 1 release note is dated October 12, 2026. It lists only one fixed issue, a generic "Fixed security vulnerabilities."

Synology fixed the flaw quietly, shipping the patch first and publishing the CVE details afterward. Devices that installed these October updates were protected before the CVE was announced. An October release note that does not mention a CVE number does not mean the device is unprotected. Check the version string instead.

How the update is packaged

For each fixed build, the archive offers two kinds of files:

  • Critical update packs (criticalupdate/update_pack), roughly 8 to 45 MB depending on branch and model. These update a device that is already on the same base build.
  • Full .pat release images, roughly 380 to 450 MB. These are mainly for models that need a full system image.

Per the release notes, the 7.4.1 update restarts the NAS. DSM may also not offer the update automatically, for example during a staged regional rollout. In that case you can install the .pat file from the archive manually.

Installing the update

Synology's update documentation describes these steps:

  1. Back up first. Synology says updates do not affect stored data but strongly recommends a backup.
  2. Get the right file for your model. In Synology Download Center, select the product type and model, then download the DSM file under Operating System.
  3. Install it. Choose Manual DSM Update, click Browse, select the file and proceed. The system restarts automatically when installation finishes.
  4. Turn on automatic security updates. In Update Settings, configure automatic installation of important updates.

Keep these constraints in mind:

  • Updates are irreversible, and only newer versions can be installed.
  • Which updates are available depends on system compatibility.
  • Automatic installation does not move a NAS to a new major version.

For these reasons, the automatic update setting alone does not prove a device is protected. Verify the build against the thresholds above.

Additional protections

Synology's general security guidance also recommends:

  • Opening router ports only for services you need
  • Enabling the firewall
  • Disabling the default admin account and using strong passwords with additional authentication
  • Enabling Auto Block and Account Protection
  • Running Security Advisor
  • Keeping multiple backup versions with Hyper Backup

These measures do not substitute for the update. Protections against password guessing, in particular, do not address a flaw whose vector requires no privileges.

Credit

Synology credits Nguyễn Bá Nam Dũng and Hà Thế Long of Viettel Cyber Security, and Warisse Valentin (Aytio), for the issues fixed in Synology_SA_26_19.

Affected systems and versions

Synology DiskStation Manager (DSM), Auth API component:

  • DSM 7.2.1: builds before 7.2.1-69057-13
  • DSM 7.2.2: builds before 7.2.2-72806-10
  • DSM 7.3: builds before 7.3.2-86009-5
  • DSM 7.4: builds before 7.4.1-90080-1

The CVE record lists releases earlier than 7.2.1 as "unknown", not as explicitly unaffected. Owners of older systems should not assume they are safe.

No special configuration is required. The vector describes a network-reachable, unauthenticated attack against the Auth API.

Vendor security history

Synology is a Taiwan-based company founded in 2000. Its products cover storage, backup, collaboration, video management and network infrastructure. In an April 13, 2026 announcement, it reported customers in over 120 countries, over 14 million deployments and use by more than half of the Fortune 500. These are vendor figures, not counts of systems affected by this CVE. The same announcement noted Synology's inclusion in CRN's 2026 Storage 100 list.

Three past incidents are relevant, each with a different cause:

  • SynoLocker (August 2014): ransomware attacked older DSM installations through two vulnerabilities that had been fixed in November and December 2013. Synology stated it could not decrypt files that were already encrypted. A fix being available is not the same as a fix being installed.
  • StealthWorker (August 2021): Synology PSIRT reported a rise in brute-force attacks and explicitly said it saw no sign of software vulnerability exploitation. Infected devices guessed common administrative credentials. Synology worked with CERT organizations to disrupt command-and-control servers and notified customers who may have been affected.
  • C3RB3R (November 2026): reporting dated November 3, 2026 describes ransomware attacks on outdated DSM versions through a vulnerability patched in December 2024. Synology did not disclose which flaw was used, and it urged users to update DSM and enable automatic updates. Nothing links this campaign to CVE-2026-76954, and its reported artifacts are not indicators for this CVE.

Vulnerable NAS devices running old software have been attacked repeatedly. That history supports prompt patching, but it does not show that this SQL injection is being used in any current campaign.

References

Detect & fix
what others miss

Works with
  • GitHub
  • GitLab
  • Bitbucket
  • Azure DevOps Services
  • Gerrit
  • CVS
  • Jira
  • Linear
  • Slack
  • Security Compass
Explore integrations
Security magnifying glass visualization