<?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://db.gcve.eu</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>Tue, 10 Nov 2026 05:29:37 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-96285</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-96285</link>
      <description>&lt;p&gt;Apache Airflow 3.3.1 shipped a fix for CVE-2026-67260 that checks the scheduler&amp;#39;s decoded `next_kwargs` value is a dictionary, but performs that check only after deserializing the whole stored payload. Deserialization reconstructs nested objects of classes permitted by the deserialization allow-list — which by default includes Airflow&amp;#39;s own classes — and runs their constructors inside the scheduler process before the check can reject the value. A Dag author, who controls a task&amp;#39;s `next_kwargs` through the task execution API, can therefore still trigger constructor execution in the scheduler when the `awaiting_input` timeout sweep processes the task, and in the API server when the task instance is served to a worker using an older Execution API version; no non-default configuration is required. Versions before 3.3.0 are not affected. This is an incomplete fix for CVE-2026-67260: deployments that upgraded to 3.3.1 for that issue must also upgrade to apache-airflow 3.4.0 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Airflow 3.3.1 shipped a fix for CVE-2026-67260 that checks the scheduler&amp;#39;s decoded `next_kwargs` value is a dictionary, but performs that check only after deserializing the whole stored payload. Deserialization reconstructs nested objects of classes permitted by the deserialization allow-list — which by default includes Airflow&amp;#39;s own classes — and runs their constructors inside the scheduler process before the check can reject the value. A Dag author, who controls a task&amp;#39;s `next_kwargs` through the task execution API, can therefore still trigger constructor execution in the scheduler when the `awaiting_input` timeout sweep processes the task, and in the API server when the task instance is served to a worker using an older Execution API version; no non-default configuration is required. Versions before 3.3.0 are not affected. This is an incomplete fix for CVE-2026-67260: deployments that upgraded to 3.3.1 for that issue must also upgrade to apache-airflow 3.4.0 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-96285</guid>
    </item>
    <item>
      <title>GHSA-h6xc-w3fp-2wwj</title>
      <link>https://db.gcve.eu/vuln/ghsa-h6xc-w3fp-2wwj</link>
      <description>&lt;p&gt;Apache Airflow 3.3.1 shipped a fix for CVE-2026-67260 that checks the scheduler&amp;#39;s decoded `next_kwargs` value is a dictionary, but performs that check only after deserializing the whole stored payload. Deserialization reconstructs nested objects of classes permitted by the deserialization allow-list — which by default includes Airflow&amp;#39;s own classes — and runs their constructors inside the scheduler process before the check can reject the value. A Dag author, who controls a task&amp;#39;s `next_kwargs` through the task execution API, can therefore still trigger constructor execution in the scheduler when the `awaiting_input` timeout sweep processes the task, and in the API server when the task instance is served to a worker using an older Execution API version; no non-default configuration is required. Versions before 3.3.0 are not affected. This is an incomplete fix for CVE-2026-67260: deployments that upgraded to 3.3.1 for that issue must also upgrade to apache-airflow 3.4.0 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Airflow 3.3.1 shipped a fix for CVE-2026-67260 that checks the scheduler&amp;#39;s decoded `next_kwargs` value is a dictionary, but performs that check only after deserializing the whole stored payload. Deserialization reconstructs nested objects of classes permitted by the deserialization allow-list — which by default includes Airflow&amp;#39;s own classes — and runs their constructors inside the scheduler process before the check can reject the value. A Dag author, who controls a task&amp;#39;s `next_kwargs` through the task execution API, can therefore still trigger constructor execution in the scheduler when the `awaiting_input` timeout sweep processes the task, and in the API server when the task instance is served to a worker using an older Execution API version; no non-default configuration is required. Versions before 3.3.0 are not affected. This is an incomplete fix for CVE-2026-67260: deployments that upgraded to 3.3.1 for that issue must also upgrade to apache-airflow 3.4.0 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-h6xc-w3fp-2wwj</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4401 — Apache Airflow: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4401</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen sowie Daten zu manipulieren oder offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen sowie Daten zu manipulieren oder offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4401</guid>
    </item>
  </channel>
</rss>
