<?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>Mon, 05 Oct 2026 11:30:07 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-04611</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-04611</link>
      <description>bdu:2022-04611</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-04611</guid>
    </item>
    <item>
      <title>BIT-airflow-2020-11982</title>
      <link>https://cve.radiocsirt.org/vuln/bit-airflow-2020-11982</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-airflow-2020-11982</guid>
    </item>
    <item>
      <title>certfr-2022-avi-525 — De multiples vulnérabilités ont été découvertes dans les produits
Fortinet. Certaines d'entre elles permettent à un att…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2022-avi-525</link>
      <description>certfr-2022-avi-525</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2022-avi-525</guid>
    </item>
    <item>
      <title>cnvd-2020-44094</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-44094</link>
      <description>cnvd-2020-44094</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-44094</guid>
    </item>
    <item>
      <title>EUVD-2026-40997</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-40997</link>
      <description>EUVD-2026-40997</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-40997</guid>
    </item>
    <item>
      <title>fkie_cve-2020-11982</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-11982</link>
      <description>&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-11982</guid>
    </item>
    <item>
      <title>GHSA-9g2w-5f3v-mfmm — Insecure default config of Celery worker in Apache Airflow</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9g2w-5f3v-mfmm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9g2w-5f3v-mfmm</guid>
    </item>
    <item>
      <title>gsd-2020-11982</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-11982</link>
      <description>gsd-2020-11982</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-11982</guid>
    </item>
    <item>
      <title>PYSEC-2020-16</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2020-16</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;An issue was found in Apache Airflow versions 1.10.10 and below. When using CeleryExecutor, if an attack can connect to the broker (Redis, RabbitMQ) directly, it was possible to insert a malicious payload directly to the broker which could lead to a deserialization attack (and thus remote code execution) on the Worker.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2020-16</guid>
    </item>
  </channel>
</rss>
