<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T03:28:07.610616+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/euvd-2026-392655</id>
    <title>EUVD-2026-392655</title>
    <updated>2026-11-17T03:28:07.613224+00:00</updated>
    <content>EUVD-2026-392655</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-392655"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-112955</id>
    <title>fkie_cve-2026-112955</title>
    <updated>2026-11-17T03:28:07.613254+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 3.7.1 of the import-export module, an authenticated importer can submit archives whose decompressed bytes, entry count, and entry sizes are not bounded before document-type authorization, and extraction or parsing failures can leave staging and extracted artifacts without unconditional cleanup. The already-hardened pre-authentication and write-error paths are separate, and current end-to-end denial-of-service impact from this residual path remains subject to maintainer validation. This issue is fixed in version 3.7.1.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-112955"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9g7p-m758-rp72</id>
    <title>GHSA-9g7p-m758-rp72 — ApostropheCMS: Import archives can exhaust server storage and deny service</title>
    <updated>2026-11-17T03:28:07.613284+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @apostrophecms/import-export</p>
<p>## Review scope and evidence limits</p>
<p>Package: @apostrophecms/import-export, version 3.7.0.</p>
<p>Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).</p>
<p>Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.</p>
<p>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.</p>
<p>## Import archive extraction lacks resource quotas and failure cleanup</p>
<p>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.</p>
<p>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() notifi…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9g7p-m758-rp72"/>
  </entry>
</feed>
