<?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 15:51:47 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-00683</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-00683</link>
      <description>bdu:2026-00683</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-00683</guid>
    </item>
    <item>
      <title>BIT-airflow-2025-68438 — Apache Airflow: Secrets in rendered templates could contain parts of sensitive values when truncated</title>
      <link>https://cve.radiocsirt.org/vuln/bit-airflow-2025-68438</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-airflow-2025-68438</guid>
    </item>
    <item>
      <title>cnvd-2026-09790</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-09790</link>
      <description>cnvd-2026-09790</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-09790</guid>
    </item>
    <item>
      <title>EUVD-2026-265931</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-265931</link>
      <description>EUVD-2026-265931</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-265931</guid>
    </item>
    <item>
      <title>fkie_cve-2025-68438</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-68438</link>
      <description>&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-68438</guid>
    </item>
    <item>
      <title>GHSA-3qmm-r55x-hpxx — Apache Airflow secrets in rendered templates could contain parts of sensitive values when truncated</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3qmm-r55x-hpxx</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&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;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3qmm-r55x-hpxx</guid>
    </item>
    <item>
      <title>PYSEC-2026-9</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&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;In Apache Airflow versions before 3.1.6, when rendered template fields in a Dag exceed [core] max_templated_field_length, sensitive values could be exposed in cleartext in the Rendered Templates UI. This occurred because serialization of those fields used a secrets masker instance that did not include user-registered mask_secret() patterns, so secrets were not reliably masked before truncation and display.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to 3.1.6 or later, which fixes this issue&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-9</guid>
    </item>
  </channel>
</rss>
