GHSA-9g7p-m758-rp72: Medium severity npm/@apostrophecms/import-export vulnerability
Review scope and evidence limits
Package: @apostrophecms/import-export, version 3.7.0.
Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).
Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.
The importer, gzip extractor, import permission gate, and core permission implementation have no differences between that release tag and the reviewed main. This follow-up is a static remediation review. We have not repeated the original end-to-end reproductions against the latest release or tested a deployed site. Current exploitability and impact therefore still require maintainer validation; the observations below establish that the reported security checks remain absent in public source. The original emailed PDF contains the original reproduction material. Please refer to that existing private attachment.
Import archive extraction lacks resource quotas and failure cleanup
The current gzip extractor handles destination write errors and waits for write completion; those parts of the original report should no longer be treated as unchanged. The import routes also now require a logged-in user before big-upload processing, as covered by GHSA-86wm-68pq-5jwq.
However, extract() still writes expanded archive entries without per-entry, aggregate decompressed-byte, or entry-count quotas. Archive parsing still precedes document-type authorization. If extraction or parsing fails, import() notifies and rethrows before the later storage.remove() call, with no unconditional cleanup around that lifecycle. The reported residual risk is excessive storage consumption and retained extraction/staging artifacts from authenticated imports. Handling a write error and requiring login do not enforce a storage budget.
Suggested remediation: add configurable streaming quotas based on actual decompressed bytes, cap entries and allowed entry types, bound concurrent imports, and clean local and uploadfs artifacts on every failure. Retain continuation artifacts only under explicit ownership, expiry and total-storage limits.
Source references: - Gzip extractor - Import lifecycle and cleanup - Related authentication fix
Coordination
Vivek R / Winfunc Original reporting team: Mufeed VH / Winfunc
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@apostrophecms/import-exportto a version that resolves this vulnerability.Fixed in 3.7.1 - Configuration
Add configurable streaming quotas for per-entry and aggregate decompressed bytes, cap the number of archive entries, and restrict allowed entry types.
Gzip extractor Streaming extraction quotas = Configurable limits based on actual decompressed bytes, entry count, and allowed entry types - Compensating control
Bound the number of concurrent imports to limit aggregate storage consumption.
- Compensating control
Retain continuation artifacts only under explicit ownership, expiry, and total-storage limits.
- Operational
Clean local and uploadfs extraction/staging artifacts on every failure, including failures during extraction or parsing, using unconditional import-lifecycle cleanup.
Event History
Frequently Asked Questions
What level of access does an attacker need?
The affected import routes require a logged-in user. The supplied vector indicates low privileges are required, with network access and no user interaction.
What is the expected security impact?
The reported impact is availability only: confidentiality and integrity impacts are listed as none, while availability impact is high. The review identifies missing resource quotas during gzip archive extraction.
Has the issue been confirmed in a deployed current release?
No. The follow-up was a static review of version 3.7.0 and the reviewed main branch; it did not repeat end-to-end reproductions or test a deployed site. Maintainer validation is still required for current exploitability and impact.
Are all previously reported extraction-handling problems still applicable?
No. The gzip extractor now handles destination write errors and waits for write completion, so those aspects should not be treated as unchanged. The static review found that the reported security checks remain absent in public source.