<?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 19:29:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-21342 — A Server-Side Forgery Request can be activated unmarshalling with XStream to access data streams from an arbitrary URL…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-21342</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; x-stream xstream&lt;/p&gt;
&lt;p&gt;XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream&amp;#39;s security framework with a whitelist limited to the minimal required types. If you rely on XStream&amp;#39;s default blacklist of the Security Framework, you will have to use at least version 1.4.16.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; x-stream xstream&lt;/p&gt;
&lt;p&gt;XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream&amp;#39;s security framework with a whitelist limited to the minimal required types. If you rely on XStream&amp;#39;s default blacklist of the Security Framework, you will have to use at least version 1.4.16.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-21342</guid>
    </item>
  </channel>
</rss>
