<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-21T07:31:17.864871+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-113658</id>
    <title>fkie_cve-2026-113658</title>
    <updated>2026-10-21T07:31:17.882099+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>ApostropheCMS is an open-source Node.js content management system. Prior to 4.33.0, the unauthenticated Rich Text CSV conversion route writes a multipart upload to the system temporary directory before checking its extension and does not remove the staged file when that validation rejects it. Repeated large rejected uploads, using the normal public CSRF cookie, can persistently consume temporary-disk capacity and may disrupt ApostropheCMS and other services that depend on the same partition. This issue is fixed in version 4.33.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-113658"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-qhcq-9pm2-c9w9</id>
    <title>GHSA-qhcq-9pm2-c9w9 — ApostropheCMS: Unauthenticated CSV import requests leave rejected uploads in the system temporary directory</title>
    <updated>2026-10-21T07:31:17.882174+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: apostrophe</p>
<p>### Summary</p>
<p>A rejected upload can remain in the operating system temporary directory.</p>
<p>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.</p>
<p>### Details</p>
<p>The endpoint is:</p>
<p>```text
POST /api/v1/@apostrophecms/rich-text-widget/generate-csv-table
```</p>
<p>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.</p>
<p>The route does not require an authenticated user. A normal CSRF cookie is sufficient.</p>
<p>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.</p>
<p>### Relationship to prior public work</p>
<p>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.</p>
<p>### POC</p>
<p>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:</p>
<p>```bash
dd if=/dev/zero of…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-qhcq-9pm2-c9w9"/>
  </entry>
</feed>
