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-112955 Overview
CVE-2026-112955 is a denial-of-service vulnerability in the ApostropheCMS import-export module prior to version 3.7.1. ApostropheCMS is an open-source Node.js content management system. An authenticated user with import privileges can submit archives whose decompressed byte size, entry count, and per-entry sizes are not bounded before the document-type authorization check runs. Extraction or parsing failures can also leave staging and extracted artifacts on disk without unconditional cleanup. The maintainers released a fix in @apostrophecms/import-export@3.7.1.
Critical Impact
Authenticated attackers can submit crafted import archives to exhaust CPU, memory, and disk resources on the ApostropheCMS host, degrading or halting service availability.
Affected Products
- ApostropheCMS @apostrophecms/import-export module versions prior to 3.7.1
- ApostropheCMS deployments that expose authenticated import functionality
- Node.js-based content management workflows relying on the vulnerable import pipeline
Discovery Timeline
- 2026-10-20 - CVE-2026-112955 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-112955
Vulnerability Analysis
The vulnerability resides in the archive-handling path of the import-export module. When an authenticated importer submits an archive, the module decompresses and enumerates entries before enforcing document-type authorization. Because decompressed byte size, entry count, and individual entry sizes are not bounded ahead of this check, an attacker can submit a small compressed payload that expands into a very large on-disk or in-memory footprint. This is a classic uncontrolled resource consumption pattern tracked under CWE-400.
A second residual issue compounds the impact. When extraction or parsing fails, staging directories and extracted artifacts are not unconditionally cleaned up. Repeated failed imports can therefore accumulate on-disk state, driving the host toward disk exhaustion over time.
Root Cause
The root cause is ordering and lifecycle management in the import pipeline. Resource bounds and authorization checks run after decompression and enumeration, rather than before. Error paths in extraction and parsing do not share the hardened cleanup logic already present on the pre-authentication and write-error paths, leaving orphaned staging artifacts behind.
Attack Vector
Exploitation requires network access and valid credentials with permission to submit imports. An attacker uploads a crafted archive, such as a highly compressed ZIP, that decompresses to many entries or large files. The server performs expensive decompression and filesystem work before the authorization check rejects the content, consuming CPU, memory, and disk. Repeated submissions amplify the effect and can degrade or halt the CMS.
// Conceptual flow of the vulnerable path in @apostrophecms/import-export < 3.7.1
// Archive is decompressed and enumerated BEFORE size/entry bounds and
// document-type authorization are enforced.
async function handleImport(req, archive) {
const staging = await extractArchive(archive); // no bounds on size/entries
const entries = await enumerateEntries(staging); // unbounded
for (const entry of entries) {
await parseEntry(entry); // may throw and leave staging on disk
await authorizeDocType(req, entry); // runs too late
}
}
// Source: https://github.com/apostrophecms/apostrophe/security/advisories/GHSA-9g7p-m758-rp72
Detection Methods for CVE-2026-112955
Indicators of Compromise
- Sustained spikes in CPU, memory, or disk I/O on the ApostropheCMS host correlated with authenticated requests to the import endpoint
- Growing staging or temporary directories used by @apostrophecms/import-export that are not reclaimed after request completion
- Repeated import failures from the same authenticated user or API token within short windows
Detection Strategies
- Alert on anomalous request rates or payload sizes posted to ApostropheCMS import routes by a single session or token
- Monitor process-level resource usage of the Node.js runtime hosting ApostropheCMS for abrupt sustained increases tied to import activity
- Review ApostropheCMS application logs for repeated extraction or parsing errors emitted by the import-export module
Monitoring Recommendations
- Instrument disk usage on directories used for import staging and alert on growth that is not reclaimed within an expected interval
- Record authenticated user identities, source IPs, and archive sizes for every import request to support post-incident attribution
- Forward web, application, and host telemetry to a centralized analytics pipeline for correlation across request, process, and filesystem signals
How to Mitigate CVE-2026-112955
Immediate Actions Required
- Upgrade @apostrophecms/import-export to version 3.7.1 or later across all ApostropheCMS deployments
- Audit which accounts and API tokens hold import privileges and revoke any that are not required
- Place rate limits and maximum request-size limits in front of the ApostropheCMS import endpoints at the reverse proxy or WAF layer
Patch Information
The fix ships in @apostrophecms/import-export@3.7.1. See the ApostropheCMS Import/Export Release, the GitHub Security Advisory GHSA-9g7p-m758-rp72, and the related commits 06e4b37 and 40b989b.
Workarounds
- Temporarily disable the import-export feature for untrusted accounts until the upgrade is deployed
- Enforce strict upload size limits and request timeouts at the proxy layer in front of ApostropheCMS
- Schedule a cleanup job that removes stale staging and extracted artifacts from the import directories
# Upgrade the vulnerable module in an ApostropheCMS project
npm install @apostrophecms/import-export@3.7.1
# Verify installed version
npm ls @apostrophecms/import-export
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

