<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T03:12:50.272784+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-05613</id>
    <title>bdu:2026-05613</title>
    <updated>2026-10-03T03:12:50.377227+00:00</updated>
    <content>bdu:2026-05613</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-05613"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-airflow-2026-28779</id>
    <title>BIT-airflow-2026-28779 — Apache Airflow: Path of session token in cookie does not consider base_url - session hijacking via co-hosted applicatio…</title>
    <updated>2026-10-03T03:12:50.377273+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: airflow</p>
<p>Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url.
This allows any application co-hosted under the same domain to capture valid Airflow session tokens from HTTP request headers, allowing full session takeover without attacking Airflow itself.</p>
<p>Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-airflow-2026-28779"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-hu66748</id>
    <title>CLEANSTART-2026-HU66748 — Security fix for CVE-2026-28779 applied in: airflow-3 3.1.8-r5</title>
    <updated>2026-10-03T03:12:50.377329+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: airflow-3</p>
<p>Security vulnerability affects the airflow-3 package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-hu66748"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-15156</id>
    <title>cnvd-2026-15156</title>
    <updated>2026-10-03T03:12:50.377363+00:00</updated>
    <content>cnvd-2026-15156</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-15156"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-276343</id>
    <title>EUVD-2026-276343</title>
    <updated>2026-10-03T03:12:50.377383+00:00</updated>
    <content>EUVD-2026-276343</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-276343"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-28779</id>
    <title>fkie_cve-2026-28779</title>
    <updated>2026-10-03T03:12:50.377401+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url.
This allows any application co-hosted under the same domain to capture valid Airflow session tokens from HTTP request headers, allowing full session takeover without attacking Airflow itself.</p>
<p>Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-28779"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4fhm-p86v-hwpx</id>
    <title>GHSA-4fhm-p86v-hwpx — Apache Airflow: Path of session token in cookie does not consider base_url - session hijacking via co-hosted applicatio…</title>
    <updated>2026-10-03T03:12:50.377442+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow</p>
<p>Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url.
This allows any application co-hosted under the same domain to capture valid Airflow session tokens from HTTP request headers, allowing full session takeover without attacking Airflow itself.</p>
<p>Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4fhm-p86v-hwpx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-16</id>
    <title>PYSEC-2026-16</title>
    <updated>2026-10-03T03:12:50.377482+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-airflow</p>
<p>Apache Airflow versions 3.1.0 through 3.1.7 session token (_token) in cookies is set to path=/ regardless of the configured [webserver] base_url or [api] base_url.
 This allows any application co-hosted under the same domain to capture valid Airflow session tokens from HTTP request headers, allowing full session takeover without attacking Airflow itself.</p>
<p>Users are recommended to upgrade to Apache Airflow 3.1.8 or later, which resolves this issue.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-16"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0755</id>
    <title>WID-SEC-W-2026-0755 — Apache Airflow: Mehrere Schwachstellen</title>
    <updated>2026-10-03T03:12:50.377518+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in Apache Airflow ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0755"/>
  </entry>
</feed>
