<?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, 17 Oct 2026 13:15:58 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-21478</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-21478</link>
      <description>cnvd-2020-21478</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-21478</guid>
    </item>
    <item>
      <title>EUVD-2026-40002</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-40002</link>
      <description>EUVD-2026-40002</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-40002</guid>
    </item>
    <item>
      <title>fkie_cve-2020-10697</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-10697</link>
      <description>&lt;p&gt;A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-10697</guid>
    </item>
    <item>
      <title>GHSA-rhg6-3qw6-38pp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rhg6-3qw6-38pp</link>
      <description>&lt;p&gt;A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rhg6-3qw6-38pp</guid>
    </item>
    <item>
      <title>gsd-2020-10697</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-10697</link>
      <description>gsd-2020-10697</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-10697</guid>
    </item>
  </channel>
</rss>
