CVE-2026-113658

### Summary A rejected upload can remain in the operating system temporary directory. Multer writes the file before its extension is checked, and the rejection path does not remove that temporary file. An unauthenticated requester can repeat this with large files and steadily consume temporary disk space. ### Details The endpoint is: ```text POST /api/v1/@apostrophecms/rich-text-widget/generate-csv-table ``` In `packages/apostrophe/modules/@apostrophecms/rich-text-widget/lib/apiRoutes.js`, Multer first writes the upload to `os.tmpdir()`. The handler then rejects filenames whose extension is not `csv`, but there is no cleanup of the Multer file on this error path. The route does not require an authenticated user. A normal CSRF cookie is sufficient. During testing, the request returned HTTP 400 with `Only csv files are supported`, while the complete uploaded content remained in a randomly named file in the configured temporary directory after the response. ### Relationship to prior public work I reviewed [PR #5013](https://github.com/apostrophecms/apostrophe/pull/5013), which migrated the Rich Text CSV upload path from `connect-multiparty` to Multer. This report concerns cleanup after that migration: the rejected Multer file remains on disk, a behavior not described in the PR or its review discussion. ### POC Create a small test file. A larger file can be used to demonstrate disk growth, but 1 MiB is enough for a safe local reproduction: ```bash dd if=/dev/zero of=rejected.txt bs=1M count=1 ``` Obtain the normal site cookies and send the rejected upload: ```bash curl -c cookies.txt 'http://127.0.0.1:3000/' > /dev/null curl -i -b cookies.txt \ -F '[email protected];filename=rejected.txt;type=text/plain' \ 'http://127.0.0.1:3000/api/v1/@apostrophecms/rich-text-widget/generate-csv-table' ``` The response is HTTP 400. Compare the contents of the system temporary directory before and after the request: ```bash ls -lt /tmp ``` A new randomly named fi