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-113656 Overview
CVE-2026-113656 affects the ApostropheCMS Form add-on, an extension for the open-source Node.js content management system ApostropheCMS. The form submission route stages unbounded multipart uploads before performing form validation or authentication. The route also lacks limits on upload size, upload count, and request rate. Repeated unauthenticated submissions can exhaust temporary disk storage and disrupt form handling or other services running on the host. The issue is tracked under CWE-770: Allocation of Resources Without Limits or Throttling and is resolved in ApostropheCMS Form 1.5.5.
Critical Impact
Unauthenticated remote attackers can submit arbitrary multipart form data to exhaust temporary disk capacity, degrading or disrupting availability of form handling and co-resident host services.
Affected Products
- ApostropheCMS Form add-on versions prior to 1.5.5
- ApostropheCMS deployments exposing form submission endpoints to unauthenticated users
- Node.js hosts running co-resident services that share temporary storage with the ApostropheCMS process
Discovery Timeline
- 2026-10-20 - CVE-2026-113656 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113656
Vulnerability Analysis
The ApostropheCMS Form add-on exposes a submission route that accepts multipart form data. Multipart parsing in the route writes uploaded parts to temporary disk storage before any validation, authentication check, or quota enforcement occurs. Because the route accepts submissions from unauthenticated clients, an attacker can repeatedly POST large or numerous parts to grow the staging directory without bound. The result is a disk resource exhaustion condition that affects not only the application's form intake path but also any other process sharing the same filesystem for temporary files, logs, or caches.
Root Cause
The root cause is improper resource allocation [CWE-770]. The submission handler does not enforce an upload size cap, a per-request part count cap, or a request rate limit. Validation and authentication logic runs after bytes are already persisted to disk, so rejected requests still consume storage. There is no cleanup guarantee tied to request outcome before the staging write completes.
Attack Vector
The attack vector is network-reachable and requires no authentication or user interaction. An attacker scripts repeated POST requests to the form submission endpoint, sending large multipart bodies or high volumes of smaller parts. Each request stages data to the temporary directory. Sustained traffic fills the volume, after which disk writes across the host begin to fail. This produces denial of service against form submissions and may cascade into other services on the same host.
// Patch excerpt from packages/ai-helper/modules/@apostrophecms/ai-helper-image/index.js
// Captures the cleanup interval handle so scheduled resource cleanup can be
// cancelled or audited, part of the broader resource-management hardening.
methods(self) {
return {
scheduleCleanup() {
// Before: setInterval(self.cleanup, 1000 * 60 * 60);
self.cleanupInterval = setInterval(self.cleanup, 1000 * 60 * 60);
},
async cleanup() {
// ...
}
};
}
// Source: https://github.com/apostrophecms/apostrophe/commit/f84fd41cbf6c22eb8d0008fc9c25df1f7130b350
Detection Methods for CVE-2026-113656
Indicators of Compromise
- Rapid growth of the Node.js process temporary directory (for example /tmp or OS tempdir) containing partial multipart staging files.
- High volumes of unauthenticated POST requests to the ApostropheCMS form submission route from a small set of source addresses.
- Disk-full errors (ENOSPC) in ApostropheCMS logs or in co-resident service logs on the same host.
Detection Strategies
- Alert on sustained POST request rates to form submission endpoints from a single IP or ASN that exceed baseline by a defined threshold.
- Monitor average and maximum Content-Length for requests to form routes and flag anomalies.
- Correlate web server access logs with filesystem usage metrics to identify upload-driven disk growth.
Monitoring Recommendations
- Instrument the temporary upload directory with disk utilization alerts at 70%, 85%, and 95% thresholds.
- Ship ApostropheCMS access logs and OS-level filesystem metrics to a centralized analytics platform for correlation.
- Track process-level file descriptor and open-file counts for the Node.js runtime hosting ApostropheCMS.
How to Mitigate CVE-2026-113656
Immediate Actions Required
- Upgrade the @apostrophecms/form package to version 1.5.5 or later on all affected deployments.
- Place a reverse proxy or web application firewall in front of ApostropheCMS to enforce request size and rate limits on form submission routes.
- Isolate the ApostropheCMS temporary upload directory onto a dedicated volume so disk exhaustion cannot impact other services.
Patch Information
The fix is shipped in ApostropheCMS Form Release 1.5.5. Supporting changes are in ApostropheCMS Commit 9500b8b and ApostropheCMS Commit f84fd41c. Full advisory details are in GitHub Security Advisory GHSA-89mh-mm8c-mv7f.
Workarounds
- Enforce client_max_body_size (nginx) or equivalent request size limits at the reverse proxy for the form submission path.
- Apply per-IP rate limiting and connection concurrency caps for the form endpoint until the patched version is deployed.
- Require authentication, CAPTCHA, or a signed token in front of form submission routes where business logic permits.
# nginx example: constrain body size and rate for the ApostropheCMS form route
limit_req_zone $binary_remote_addr zone=apos_form:10m rate=5r/m;
server {
# ...
location /api/v1/@apostrophecms/form/submit {
client_max_body_size 1m;
limit_req zone=apos_form burst=3 nodelay;
proxy_pass http://apostrophecms_upstream;
}
}
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

