<?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-06T22:28:51.628191+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:2023-02828</id>
    <title>bdu:2023-02828</title>
    <updated>2026-10-06T22:28:51.632352+00:00</updated>
    <content>bdu:2023-02828</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2023-02828"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bit-superset-2023-27524</id>
    <title>BIT-superset-2023-27524 — Apache Superset: Session validation vulnerability when using provided default SECRET_KEY</title>
    <updated>2026-10-06T22:28:51.632384+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: superset</p>
<p>Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.</p>
<p>All superset installations should always set a unique secure random SECRET_KEY. Your SECRET_KEY is used to securely sign all session cookies and encrypting sensitive information on the database.
Add a strong SECRET_KEY to your `superset_config.py` file like:</p>
<p>SECRET_KEY = &lt;YOUR_OWN_RANDOM_GENERATED_SECRET_KEY&gt;</p>
<p>Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-superset-2023-27524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-255753</id>
    <title>EUVD-2026-255753</title>
    <updated>2026-10-06T22:28:51.632430+00:00</updated>
    <content>EUVD-2026-255753</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-255753"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2023-27524</id>
    <title>fkie_cve-2023-27524</title>
    <updated>2026-10-06T22:28:51.632444+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.</p>
<p>All superset installations should always set a unique secure random SECRET_KEY. Your SECRET_KEY is used to securely sign all session cookies and encrypting sensitive information on the database.
Add a strong SECRET_KEY to your `superset_config.py` file like:</p>
<p>SECRET_KEY = &lt;YOUR_OWN_RANDOM_GENERATED_SECRET_KEY&gt;</p>
<p>Alternatively you can set it with `SUPERSET_SECRET_KEY` environment variable.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2023-27524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5cx2-vq3h-x52c</id>
    <title>GHSA-5cx2-vq3h-x52c — Apache superset missing check for default SECRET_KEY</title>
    <updated>2026-10-06T22:28:51.632470+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-superset</p>
<p>Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5cx2-vq3h-x52c"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2023-27524</id>
    <title>gsd-2023-27524</title>
    <updated>2026-10-06T22:28:51.632490+00:00</updated>
    <content>gsd-2023-27524</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2023-27524"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2026-1161</id>
    <title>PYSEC-2026-1161 — Apache superset missing check for default SECRET_KEY</title>
    <updated>2026-10-06T22:28:51.632501+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: apache-superset</p>
<p>Session Validation attacks in Apache Superset versions up to and including 2.0.1. Installations that have not altered the default configured SECRET_KEY according to installation instructions allow for an attacker to authenticate and access unauthorized resources. This does not affect Superset administrators who have changed the default value for SECRET_KEY config.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2026-1161"/>
  </entry>
</feed>
