<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 16:45:25 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-26142</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-26142</link>
      <description>cnvd-2021-26142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-26142</guid>
    </item>
    <item>
      <title>EUVD-2026-22170</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-22170</link>
      <description>EUVD-2026-22170</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-22170</guid>
    </item>
    <item>
      <title>fkie_cve-2021-21359</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-21359</link>
      <description>&lt;p&gt;TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 9.5.25, 10.4.14, 11.1.1 requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded. This is fixed in versions 9.5.25, 10.4.14, 11.1.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 9.5.25, 10.4.14, 11.1.1 requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded. This is fixed in versions 9.5.25, 10.4.14, 11.1.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-21359</guid>
    </item>
    <item>
      <title>GHSA-4p9g-qgx9-397p — Denial of Service in Page Error Handling</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4p9g-qgx9-397p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core, Packagist: typo3/cms&lt;/p&gt;
&lt;p&gt;&amp;gt; ### Meta
&amp;gt; * CVSS:  `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C` (5.5)
&amp;gt; * CWE-405, CWE-674
&amp;gt; * Status: **DRAFT**&lt;/p&gt;
&lt;p&gt;### Problem
Requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content  to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to Paul Keller, Mathias Bolt Lesniak and Kay Strobach who reported this issue and to TYPO3 framework merger Frank Nägler and to TYPO3 security team member Torben Hansen who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2021-005](https://typo3.org/security/advisory/typo3-core-sa-2021-005)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: typo3/cms-core, Packagist: typo3/cms&lt;/p&gt;
&lt;p&gt;&amp;gt; ### Meta
&amp;gt; * CVSS:  `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C` (5.5)
&amp;gt; * CWE-405, CWE-674
&amp;gt; * Status: **DRAFT**&lt;/p&gt;
&lt;p&gt;### Problem
Requesting invalid or non-existing resources via HTTP triggers the page error handler which again could retrieve content  to be shown as error message from another page. This leads to a scenario in which the application is calling itself recursively - amplifying the impact of the initial attack until the limits of the web server are exceeded.&lt;/p&gt;
&lt;p&gt;### Solution
Update to TYPO3 versions 9.5.25, 10.4.14, 11.1.1 that fix the problem described.&lt;/p&gt;
&lt;p&gt;### Credits
Thanks to Paul Keller, Mathias Bolt Lesniak and Kay Strobach who reported this issue and to TYPO3 framework merger Frank Nägler and to TYPO3 security team member Torben Hansen who fixed the issue.&lt;/p&gt;
&lt;p&gt;### References
* [TYPO3-CORE-SA-2021-005](https://typo3.org/security/advisory/typo3-core-sa-2021-005)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4p9g-qgx9-397p</guid>
    </item>
    <item>
      <title>gsd-2021-21359</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-21359</link>
      <description>gsd-2021-21359</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-21359</guid>
    </item>
  </channel>
</rss>
