<?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>Sat, 10 Oct 2026 08:25:57 +0000</lastBuildDate>
    <item>
      <title>bdu:2023-01058</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2023-01058</link>
      <description>bdu:2023-01058</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2023-01058</guid>
    </item>
    <item>
      <title>BIT-discourse-2022-31182 — Cache poisoning via maliciously-formed request in Discourse</title>
      <link>https://cve.radiocsirt.org/vuln/bit-discourse-2022-31182</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: discourse&lt;/p&gt;
&lt;p&gt;Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse&amp;#39;s default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: discourse&lt;/p&gt;
&lt;p&gt;Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse&amp;#39;s default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-discourse-2022-31182</guid>
    </item>
    <item>
      <title>EUVD-2026-233856</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233856</link>
      <description>EUVD-2026-233856</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233856</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31182</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31182</link>
      <description>&lt;p&gt;Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse&amp;#39;s default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse&amp;#39;s default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31182</guid>
    </item>
    <item>
      <title>gsd-2022-31182</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31182</link>
      <description>gsd-2022-31182</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31182</guid>
    </item>
  </channel>
</rss>
