<?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>Wed, 07 Oct 2026 13:34:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-40690 — Apache Airflow: Assets graph view bypasses DAG level access control displaying unrelated topologies and all DAGs names…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-40690</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Airflow&lt;/p&gt;
&lt;p&gt;The asset dependency graph did not restrict nodes by the viewer&amp;#39;s DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.2.1, which fixes this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Airflow&lt;/p&gt;
&lt;p&gt;The asset dependency graph did not restrict nodes by the viewer&amp;#39;s DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.2.1, which fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-40690</guid>
    </item>
    <item>
      <title>GHSA-w7rc-q6cm-f5gm — Apache Airflow's asset dependency graph did not restrict nodes by the viewer's DAG read permissions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w7rc-q6cm-f5gm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: apache-airflow&lt;/p&gt;
&lt;p&gt;The asset dependency graph did not restrict nodes by the viewer&amp;#39;s DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.2.1, 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;The asset dependency graph did not restrict nodes by the viewer&amp;#39;s DAG read permissions: a user with read access to at least one DAG could browse the asset graph for any other asset in the deployment and learn the existence and names of DAGs and assets outside their authorized scope.&lt;/p&gt;
&lt;p&gt;Users are recommended to upgrade to version 3.2.1, which fixes this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w7rc-q6cm-f5gm</guid>
    </item>
  </channel>
</rss>
