Skip to main content
Vulnerability Database/CVE-2026-113658

CVE-2026-113658: ApostropheCMS Temporary File DoS Vulnerability

CVE-2026-113658 is a denial of service vulnerability in ApostropheCMS that allows attackers to exhaust disk space through repeated large file uploads. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113658 Overview

CVE-2026-113658 is a resource exhaustion vulnerability [CWE-400] in ApostropheCMS, an open-source Node.js content management system. The unauthenticated Rich Text CSV conversion route writes multipart uploads to the system temporary directory before validating the file extension. When validation rejects a file, the route fails to delete the staged content. Attackers can abuse this behavior using only the public CSRF cookie, submitting repeated large rejected uploads to persistently consume temporary disk capacity. The resulting disk pressure can disrupt ApostropheCMS and any co-located services sharing the same partition. The issue is fixed in version 4.33.0.

Critical Impact

An unauthenticated remote attacker can exhaust temporary disk space on the host, degrading availability of ApostropheCMS and other services on the same partition.

Affected Products

  • ApostropheCMS versions prior to 4.33.0
  • apostrophe npm package (Node.js CMS)
  • Deployments exposing the Rich Text CSV conversion route

Discovery Timeline

  • 2026-10-20 - CVE-2026-113658 published to NVD
  • 2026-10-20 - Last updated in NVD database

Technical Details for CVE-2026-113658

Vulnerability Analysis

The vulnerability resides in the Rich Text CSV conversion endpoint exposed by ApostropheCMS. The route accepts multipart uploads from unauthenticated clients that present a valid public CSRF cookie, which the server issues to any visitor. Incoming uploads are streamed to the operating system temporary directory before any content validation occurs.

After writing the file, the handler inspects the extension and rejects anything that is not a permitted CSV. However, the rejection path never removes the staged temporary file. Each rejected request leaves orphaned bytes on disk. Because the route requires no authentication, an attacker can issue repeated large uploads and inflate temporary storage until the partition is full.

This is categorized as a Denial of Service (DoS) via Resource Exhaustion. Services that depend on the same filesystem partition, including the CMS runtime itself, database sockets, logging, and session stores, may fail once the temporary directory can no longer accept writes.

Root Cause

The handler violates the principle of validate-before-persist. Multer-style multipart handling writes the body to disk prior to the extension check, and the error branch of the validator does not call an unlink on the staged path. Combined with an unauthenticated entry point, the design allows attacker-controlled growth of the temporary directory.

Attack Vector

An attacker fetches the public CSRF cookie, then issues repeated multipart POST requests to the Rich Text CSV conversion route carrying large payloads with a non-CSV extension. The server stages each payload, rejects the extension, and leaves the file behind. Repeating the request at scale consumes temporary disk capacity until writes fail across the host.

Selected patch excerpts from the upstream fix illustrate hardening around temporary artifacts and uploads:

javascript
  methods(self) {
    return {
      scheduleCleanup() {
-        setInterval(self.cleanup, 1000 * 60 * 60);
+        self.cleanupInterval = setInterval(self.cleanup, 1000 * 60 * 60);
      },

      async cleanup() {

Source: ApostropheCMS Commit Fix

text
 node_modules
 npm-debug.log
 .DS_Store
-package-lock.json
+package-lock.json
+# Test files
+test/public/uploads
+test/data

Source: ApostropheCMS ai-helper .gitignore patch

Detection Methods for CVE-2026-113658

Indicators of Compromise

  • Rapid growth of files in the OS temporary directory (/tmp on Linux, %TEMP% on Windows) owned by the Node.js process.
  • High-volume POST traffic to the ApostropheCMS Rich Text CSV conversion route from a small set of source IPs.
  • Repeated HTTP 4xx responses from the CSV conversion endpoint correlated with sustained disk writes.
  • Application errors referencing ENOSPC or failed temp-file creation across co-located services.

Detection Strategies

  • Monitor inode and byte utilization on the partition hosting the temporary directory and alert on abnormal slopes.
  • Baseline normal request rates to the CSV conversion endpoint and alert on deviations from unauthenticated sources.
  • Correlate web access logs for sustained multipart uploads with upload sizes exceeding typical content submissions.

Monitoring Recommendations

  • Collect filesystem metrics for the temporary partition and ship them to a central telemetry pipeline.
  • Enable application-level logging for upload validation rejections so repeated failures are observable.
  • Track per-source request rates to the Rich Text CSV route behind the reverse proxy or WAF.

How to Mitigate CVE-2026-113658

Immediate Actions Required

  • Upgrade the apostrophe package to version 4.33.0 or later.
  • Restart the ApostropheCMS process after upgrade to clear any lingering handles to orphaned temp files.
  • Purge accumulated artifacts from the temporary directory associated with the Node.js runtime.
  • Place the Rich Text CSV conversion route behind rate limiting at the reverse proxy or WAF.

Patch Information

The fix is included in ApostropheCMS 4.33.0. Review the upstream advisory and commits for scope and verification: GitHub Security Advisory GHSA-qhcq-9pm2-c9w9, ApostropheCMS 4.33.0 Release, ApostropheCMS Commit Fix, and ApostropheCMS Commit Update.

Workarounds

  • Mount the Node.js temporary directory on a dedicated partition isolated from database, log, and system storage.
  • Enforce request size limits on the CSV conversion endpoint at the reverse proxy or WAF layer.
  • Deploy a scheduled cleanup task that removes stale files from the temporary directory until the patched version is deployed.
  • Restrict access to the Rich Text CSV conversion route via network ACLs where public exposure is not required.
bash
# Upgrade ApostropheCMS to the patched release
npm install apostrophe@4.33.0

# Example: isolate the Node.js temp directory on Linux
export TMPDIR=/var/apostrophe-tmp
mkdir -p "$TMPDIR"
chown node:node "$TMPDIR"

# Example: periodic cleanup of stale upload stubs (older than 1 hour)
find "$TMPDIR" -type f -mmin +60 -delete

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.