PatchSiren cyber security CVE debrief
CVE-2026-67248 ASUSTOR Inc. CVE debrief
A stack-based buffer overflow vulnerability was found in the File Explorer on the ADM. The vulnerability occurs because user-controlled input is not properly validated before being decoded and copied into a fixed-size stack buffer. An authenticated attacker can exploit this issue to cause denial of service of the affected CGI process. The issue affects systems running ADM 4.1.0 through ADM 4.3.3.RUN1 and ADM 5.0.0 through ADM 5.1.3.RI81. Defenders should assess potential exposure and impact, especially for systems with File Explorer functionality.
- Vendor
- ASUSTOR Inc.
- Product
- ADM
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-30
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-07-30
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for systems with File Explorer functionality, especially those using ADM, should assess potential exposure and impact. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify exposure and assess potential impact on systems with File Explorer functionality.
Why it matters
Defenders should prioritize verifying exposure and assessing potential impact, especially for systems with File Explorer functionality, as an authenticated attacker can exploit this issue to cause denial of service.
- Denial of service of the affected CGI process
- Potential disruption to system functionality
- Need for verification of system exposure and potential impact
Technical summary
The vulnerability occurs because user-controlled input is not properly validated before being decoded and copied into a fixed-size stack buffer. An authenticated attacker can exploit this issue to cause denial of service of the affected CGI process. The issue affects systems running ADM 4.1.0 through ADM 4.3.3.RUN1 and ADM 5.0.0 through ADM 5.1.3.RI81. The vulnerability has a CVSS score of 8.7 and is classified as HIGH severity. Defenders should prioritize verifying exposure and assessing potential impact, especially for systems with File Explorer functionality.
Defensive priority
Defenders should prioritize verifying exposure and assessing potential impact, especially for systems with File Explorer functionality.
Recommended defensive actions
- Verify exposure by checking system configurations and File Explorer functionality
- Assess potential impact on systems with File Explorer functionality
- Monitor system logs for potential exploitation attempts
- 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
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
Evidence notes
The CVE record and NVD vulnerability detail page provide information on the vulnerability, including its description, CVSS score, and affected products. The CVE record was published on 2026-07-30T05:16:39.157Z and has not been modified since then. The vulnerability has a CVSS score of 8.7 and is classified as HIGH severity. The affected products and versions include ADM 4.1.0 through ADM 4.3.3.RUN1 and ADM 5.0.0 through ADM 5.1.3.RI81.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-67248 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-67248
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-67248 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-67248
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
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.