<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T11:30:09.250272+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2022-04611</id>
    <title>bdu:2022-04611</title>
    <updated>2026-10-05T11:30:09.255423+00:00</updated>
    <content>bdu:2022-04611</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2022-04611"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-airflow-2020-11982</id>
    <title>BIT-airflow-2020-11982</title>
    <updated>2026-10-05T11:30:09.255463+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: airflow</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-airflow-2020-11982"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2022-avi-525</id>
    <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>
    <updated>2026-10-05T11:30:09.255498+00:00</updated>
    <content>certfr-2022-avi-525</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2022-avi-525"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2020-44094</id>
    <title>cnvd-2020-44094</title>
    <updated>2026-10-05T11:30:09.255516+00:00</updated>
    <content>cnvd-2020-44094</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2020-44094"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-40997</id>
    <title>EUVD-2026-40997</title>
    <updated>2026-10-05T11:30:09.255528+00:00</updated>
    <content>EUVD-2026-40997</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-40997"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2020-11982</id>
    <title>fkie_cve-2020-11982</title>
    <updated>2026-10-05T11:30:09.255538+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2020-11982"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9g2w-5f3v-mfmm</id>
    <title>GHSA-9g2w-5f3v-mfmm — Insecure default config of Celery worker in Apache Airflow</title>
    <updated>2026-10-05T11:30:09.255559+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9g2w-5f3v-mfmm"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2020-11982</id>
    <title>gsd-2020-11982</title>
    <updated>2026-10-05T11:30:09.255579+00:00</updated>
    <content>gsd-2020-11982</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2020-11982"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2020-16</id>
    <title>PYSEC-2020-16</title>
    <updated>2026-10-05T11:30:09.255590+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2020-16"/>
  </entry>
</feed>
