<?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, 19 Oct 2026 22:32:40 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-03288</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03288</link>
      <description>bdu:2024-03288</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03288</guid>
    </item>
    <item>
      <title>BIT-airflow-2024-31869 — Apache Airflow: Sensitive configuration for providers displayed when "non-sensitive-only" config used</title>
      <link>https://cve.radiocsirt.org/vuln/bit-airflow-2024-31869</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-airflow-2024-31869</guid>
    </item>
    <item>
      <title>cnvd-2024-20804</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2024-20804</link>
      <description>cnvd-2024-20804</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2024-20804</guid>
    </item>
    <item>
      <title>EUVD-2026-222471</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-222471</link>
      <description>EUVD-2026-222471</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-222471</guid>
    </item>
    <item>
      <title>fkie_cve-2024-31869</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-31869</link>
      <description>&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-31869</guid>
    </item>
    <item>
      <title>GHSA-2522-mrjc-m688 — Apache Airflow: Sensitive configuration for providers displayed when "non-sensitive-only" config used</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2522-mrjc-m688</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&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;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2522-mrjc-m688</guid>
    </item>
    <item>
      <title>gsd-2024-31869</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-31869</link>
      <description>gsd-2024-31869</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-31869</guid>
    </item>
    <item>
      <title>PYSEC-2026-1128 — Apache Airflow: Sensitive configuration for providers displayed when "non-sensitive-only" config used</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1128</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&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;Airflow versions 2.7.0 through 2.8.4 have a vulnerability that allows an authenticated user to see sensitive provider configuration via the &amp;#34;configuration&amp;#34; UI page when &amp;#34;non-sensitive-only&amp;#34; was set as &amp;#34;webserver.expose_config&amp;#34; configuration (The celery provider is the only community provider currently that has sensitive configurations). You should migrate to Airflow 2.9 or change your &amp;#34;expose_config&amp;#34; configuration to False as a workaround. This is similar, but different to  CVE-2023-46288 https://github.com/advisories/GHSA-9qqg-mh7c-chfq  which concerned API, not UI configuration page.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1128</guid>
    </item>
  </channel>
</rss>
