<?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-03T04:57:10.007106+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:2026-09198</id>
    <title>bdu:2026-09198</title>
    <updated>2026-10-03T04:57:10.135028+00:00</updated>
    <content>bdu:2026-09198</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-09198"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-he71262</id>
    <title>CLEANSTART-2026-HE71262 — Security fix for CVE-2026-49486 applied in: airflow-3 3.0.6-r1, airflow-3 3.1.8-r5</title>
    <updated>2026-10-03T04:57:10.135079+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: airflow-3</p>
<p>CVE-2026-49486 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-he71262"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-369565</id>
    <title>EUVD-2026-369565</title>
    <updated>2026-10-03T04:57:10.135129+00:00</updated>
    <content>EUVD-2026-369565</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-369565"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49486</id>
    <title>fkie_cve-2026-49486</title>
    <updated>2026-10-03T04:57:10.135150+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The Apache Airflow FTP provider's `FTPSHook.get_conn()` created an `ftplib.FTP_TLS` connection but never called `prot_p()`, so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using `FTPSHook` or `FTPSFileTransmitOperator` to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to `3.15.1` or later, which issues `PROT P` to encrypt the data channel.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-49486"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fgch-86x8-fv43</id>
    <title>GHSA-fgch-86x8-fv43 — Apache Airflow FTP provider: FTP Provider does not protect FTPS data channel (missing PROT_P)</title>
    <updated>2026-10-03T04:57:10.135190+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow-providers-ftp</p>
<p>The Apache Airflow FTP provider's `FTPSHook.get_conn()` created an `ftplib.FTP_TLS` connection but never called `prot_p()`, so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using `FTPSHook` or `FTPSFileTransmitOperator` to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to `3.15.1` or later, which issues `PROT P` to encrypt the data channel.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fgch-86x8-fv43"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-238</id>
    <title>PYSEC-2026-238</title>
    <updated>2026-10-03T04:57:10.135243+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow-providers-ftp</p>
<p>The Apache Airflow FTP provider's `FTPSHook.get_conn()` created an `ftplib.FTP_TLS` connection but never called `prot_p()`, so although the control channel was TLS-protected the data channel was transmitted in cleartext. Any deployment using `FTPSHook` or `FTPSFileTransmitOperator` to move files over FTPS exposed file contents and credentials-in-transit to a network attacker able to observe the data connection. Upgrade apache-airflow-providers-ftp to `3.15.1` or later, which issues `PROT P` to encrypt the data channel.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-238"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2097</id>
    <title>WID-SEC-W-2026-2097 — Apache Airflow FTP Provider: Schwachstelle ermöglicht Offenlegung von Informationen</title>
    <updated>2026-10-03T04:57:10.135279+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache Airflow FTP Provider ausnutzen, um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2097"/>
  </entry>
</feed>
