<?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>Mon, 28 Sep 2026 13:09:37 +0000</lastBuildDate>
    <item>
      <title>BIT-airflow-2026-75157 — Apache Airflow: Asset queued-events DELETE endpoints gated on Dag READ instead of Dag EDIT (asset-triggered scheduling…</title>
      <link>https://db.gcve.eu/vuln/bit-airflow-2026-75157</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: airflow&lt;/p&gt;
&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bit-airflow-2026-75157</guid>
    </item>
    <item>
      <title>fkie_cve-2026-75157</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-75157</link>
      <description>&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-75157</guid>
    </item>
    <item>
      <title>GHSA-gmw9-258q-r8gm</title>
      <link>https://db.gcve.eu/vuln/ghsa-gmw9-258q-r8gm</link>
      <description>&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Apache Airflow&amp;#39;s asset queued-events DELETE endpoints checked the caller&amp;#39;s Dag-axis permission with `READ` instead of `EDIT`. Any authenticated user who could read a Dag could therefore delete that Dag&amp;#39;s queued asset events, silently suppressing asset-triggered scheduling for it — a state-changing action gated on a read-only permission. Deployments are affected whenever asset-triggered scheduling is in use and Dag read access is granted more widely than Dag edit access, which is the normal RBAC arrangement; no special configuration is required. Upgrade to apache-airflow 3.3.2 or later.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gmw9-258q-r8gm</guid>
    </item>
  </channel>
</rss>
