PatchSiren cyber security CVE debrief
CVE-2026-13673 Synology CVE debrief
CVE-2026-13673 is an incorrect permission assignment for critical resource vulnerability in LDAP API in Synology DiskStation Manager (DSM). This vulnerability allows remote authenticated users to read or write arbitrary files and conduct denial-of-service attacks. System administrators and security teams should assess exposure, verify DSM versions, and apply necessary updates or mitigations. The CVE record and NVD entry provide details on the vulnerability, but do not specify versions, exploitation, impact, or remediation beyond vendor advisories.
- Vendor
- Synology
- Product
- DiskStation Manager (DSM)
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-18
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-18
- Advisory updated
- 2026-09-18
Who should care
System administrators and security teams responsible for Synology DiskStation Manager (DSM) deployments should assess exposure and apply necessary updates or mitigations. This includes verifying DSM versions, reviewing and limiting LDAP API access, and monitoring for suspicious activity.
Why it matters
CVE-2026-13673 is a high-severity vulnerability in Synology DiskStation Manager (DSM) that allows remote authenticated users to read or write arbitrary files and conduct denial-of-service attacks. System administrators and security teams should assess exposure, verify DSM versions, and apply necessary updates or mitigations.
- Remote authenticated users may read or write arbitrary files
- Denial-of-service attacks may be conducted
- Verification of DSM versions and patch levels is necessary
- Remediation priority is high due to potential for significant impact
Technical summary
CVE-2026-13673 is an incorrect permission assignment for critical resource vulnerability in LDAP API in Synology DiskStation Manager (DSM) before 7.2.1-69057-12, 7.2.2-72806-9, 7.3.2-86009-4 and 7.4-90075. This allows remote authenticated users to read or write arbitrary files and conduct denial-of-service attacks. System administrators and security teams should assess exposure, verify DSM versions, and apply necessary updates or mitigations. Verification of DSM versions and patch levels is necessary. Remediation priority is high due to potential for significant impact.
Defensive priority
High
Recommended defensive actions
- Review and apply Synology's security advisories for DSM
- Verify and limit LDAP API access
- Monitor for suspicious activity
- Update DSM to the latest version
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but do not specify versions, exploitation, impact, or remediation beyond vendor advisories. Synology security advisories should be reviewed for specific DSM versions and patch levels. Verification of DSM versions and patch levels is necessary. Remediation priority is high due to potential for significant impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-13673 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-13673
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-13673 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-13673
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.synology.com/en-global/security/advisory/Synology_SA_26_13
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.