<?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>Thu, 22 Oct 2026 22:34:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-43791 — Label Studio has Hardcoded Django `SECRET_KEY` that can be Abused to Forge Session Tokens</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-43791</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HumanSignal label-studio&lt;/p&gt;
&lt;p&gt;Label Studio is a multi-type data labeling and annotation tool with standardized output format. There is a vulnerability that can be chained within the ORM Leak vulnerability to impersonate any account on Label Studio. An attacker could exploit these vulnerabilities to escalate their privileges from a low privilege user to a Django Super Administrator user. The vulnerability was found to affect versions before `1.8.2`, where a patch was introduced.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; HumanSignal label-studio&lt;/p&gt;
&lt;p&gt;Label Studio is a multi-type data labeling and annotation tool with standardized output format. There is a vulnerability that can be chained within the ORM Leak vulnerability to impersonate any account on Label Studio. An attacker could exploit these vulnerabilities to escalate their privileges from a low privilege user to a Django Super Administrator user. The vulnerability was found to affect versions before `1.8.2`, where a patch was introduced.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-43791</guid>
    </item>
    <item>
      <title>GHSA-f475-x83m-rx5m — Label Studio has Hardcoded Django `SECRET_KEY` that can be Abused to Forge Session Tokens</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f475-x83m-rx5m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: label-studio&lt;/p&gt;
&lt;p&gt;# Introduction&lt;/p&gt;
&lt;p&gt;This write-up describes a vulnerability found in [Label Studio](https://github.com/HumanSignal/label-studio), a popular open source data labeling tool. The vulnerability was found to affect versions before `1.8.2`, where a patch was introduced.&lt;/p&gt;
&lt;p&gt;# Overview&lt;/p&gt;
&lt;p&gt;In [Label Studio version 1.8.1](https://github.com/HumanSignal/label-studio/tree/1.8.1), a hard coded Django `SECRET_KEY` was set in the application settings. The Django `SECRET_KEY` is used for signing session tokens by the web application framework, and should never be shared with unauthorised parties.&lt;/p&gt;
&lt;p&gt;However, the Django framework inserts a `_auth_user_hash` claim in the session token that is a HMAC hash of the account&amp;#39;s password hash. That claim would normally prevent forging a valid Django session token without knowing the password hash of the account. However, any authenticated user can exploit an Object Relational Mapper (ORM) Leak vulnerability in Label Studio to leak the password hash of any account on the platform, which is reported as a separate vulnerability. An attacker can exploit the ORM Leak vulnerability (which was patched in [`1.9.2post0`](https://github.com/HumanSignal/label-studio/releases/tag/1.9.2.post0)) and forge session tokens for all users on Label Studio using the hard coded `SECRET_KEY`.&lt;/p&gt;
&lt;p&gt;# Description&lt;/p&gt;
&lt;p&gt;Below is the code snippet of the Django settings file at [`label_studio/core/settings/base.py`](https://github.com/HumanSignal/label-studio/blob/1.8.1/label_studio/core/settings…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: label-studio&lt;/p&gt;
&lt;p&gt;# Introduction&lt;/p&gt;
&lt;p&gt;This write-up describes a vulnerability found in [Label Studio](https://github.com/HumanSignal/label-studio), a popular open source data labeling tool. The vulnerability was found to affect versions before `1.8.2`, where a patch was introduced.&lt;/p&gt;
&lt;p&gt;# Overview&lt;/p&gt;
&lt;p&gt;In [Label Studio version 1.8.1](https://github.com/HumanSignal/label-studio/tree/1.8.1), a hard coded Django `SECRET_KEY` was set in the application settings. The Django `SECRET_KEY` is used for signing session tokens by the web application framework, and should never be shared with unauthorised parties.&lt;/p&gt;
&lt;p&gt;However, the Django framework inserts a `_auth_user_hash` claim in the session token that is a HMAC hash of the account&amp;#39;s password hash. That claim would normally prevent forging a valid Django session token without knowing the password hash of the account. However, any authenticated user can exploit an Object Relational Mapper (ORM) Leak vulnerability in Label Studio to leak the password hash of any account on the platform, which is reported as a separate vulnerability. An attacker can exploit the ORM Leak vulnerability (which was patched in [`1.9.2post0`](https://github.com/HumanSignal/label-studio/releases/tag/1.9.2.post0)) and forge session tokens for all users on Label Studio using the hard coded `SECRET_KEY`.&lt;/p&gt;
&lt;p&gt;# Description&lt;/p&gt;
&lt;p&gt;Below is the code snippet of the Django settings file at [`label_studio/core/settings/base.py`](https://github.com/HumanSignal/label-studio/blob/1.8.1/label_studio/core/settings…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f475-x83m-rx5m</guid>
    </item>
  </channel>
</rss>
