<?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-22T01:21:42.188786+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-113711</id>
    <title>fkie_cve-2026-113711</title>
    <updated>2026-10-22T01:21:42.208822+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 of ApostropheCMS and 3.7.0 of the import-export module, import routes invoke bigUploadMiddleware without an early authorize callback, allowing unauthenticated requests to perform upload initialization, chunk storage, temporary processing, and attacker-declared cleanup work before the later user check rejects the import. This issue is fixed in ApostropheCMS 4.33.0 and import-export 3.7.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-113711"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-86wm-68pq-5jwq</id>
    <title>GHSA-86wm-68pq-5jwq — ApostropheCMS: Unauthenticated resource exhaustion via pre-auth aposBigUpload processing in @apostrophecms/import-export</title>
    <updated>2026-10-22T01:21:42.208893+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: apostrophe, npm: @apostrophecms/import-export</p>
<p>## Summary</p>
<p>A potential unauthenticated denial-of-service vulnerability exists in the chunked import upload path used by `@apostrophecms/import-export`.</p>
<p>The affected import API routes invoke:</p>
<p>`self.apos.http.bigUploadMiddleware()`</p>
<p>before the actual import handler performs its authentication check.</p>
<p>Because no `authorize` callback is supplied to `bigUploadMiddleware()`, unauthenticated requests can reach the `aposBigUpload` `start`, `chunk`, and `end` operations before the later `req.user` check rejects the import.</p>
<p>As a result, an unauthenticated remote attacker can create server-side upload state, write chunk data to upload storage, trigger temporary-file processing, and cause attacker-controlled cleanup operations before authentication is enforced.</p>
<p>## Affected Component</p>
<p>Package:</p>
<p>`@apostrophecms/import-export`</p>
<p>Confirmed affected version:</p>
<p>`3.6.2`</p>
<p>Potential earlier affected versions:</p>
<p>The issue may affect earlier 3.x releases in which the current big-upload-based import implementation is present. I have not yet fully verified the exact introduction version and recommend that the maintainers confirm the affected version range.</p>
<p>## Vulnerability Type</p>
<p>Primary:</p>
<p>**CWE-400 — Uncontrolled Resource Consumption**</p>
<p>Related:</p>
<p>**CWE-306 — Missing Authentication for Critical Function**</p>
<p>**CWE-770 — Allocation of Resources Without Limits or Throttling**</p>
<p>## Technical Details</p>
<p>The page import route registers the following middleware chain:</p>
<p>`packages/import-export/modules/@apostr…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-86wm-68pq-5jwq"/>
  </entry>
</feed>
