VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

label-studio: vulnerability history, versions and safety

label-studio is a package in the PyPI ecosystem. Vulert records 23 vulnerabilities for it across 101 releases, from Oct 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
23 vulnerabilities recorded C1 H7 M4 U11
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all label-studio vulnerabilities

Vulert verdict on label-studio 1.23.2 i

Updated on 23 Oct 2026

Careful: 1.23.2 has 5 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.23.2 — affected i
  • Vulnerabilities on record 23 over 3 years · 4 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 2 packages i
  • Stars 28,527 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for label-studio, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.23.2 29 Sep 2026 H1 U4 Apache-2.0 No Details →
1.23.1 25 Sep 2026 H1 U4 Apache-2.0 No Details →
1.23.0 13 Mar 2026 H1 U4 Apache-2.0 No Details →
1.22.0 19 Dec 2025 H1 U1 Apache-2.0 No Details →
1.21.0 30 Sep 2025 H1 U1 Apache-2.0 No Details →
1.20.0 01 Jul 2025 H1 U1 Apache-2.0 No Details →
1.19.0 10 Jun 2025 H1 U1 Apache-2.0 No Details →
1.18.0 14 May 2025 H1 U1 Apache-2.0 No Details →
1.17.0 07 Apr 2025 H2 U2 Apache-2.0 No Details →
1.16.0 13 Feb 2025 H2 U2 Apache-2.0 No Details →
1.15.0 11 Dec 2024 H3 M1 U4 Apache-2.0 No Details →
1.14.0.post0 13 Nov 2024 H3 M1 U4 Apache-2.0 No Details →
1.14.0 04 Nov 2024 H3 M1 U4 Apache-2.0 No Details →
1.13.1 20 Aug 2024 H3 M1 U4 Apache-2.0 No Details →
1.13.0 31 Jul 2024 H3 M1 U4 Apache-2.0 No Details →
1.12.1 21 May 2024 H3 M1 U4 Apache-2.0 No Details →
1.12.0.post0 06 May 2024 H3 M1 U4 Apache-2.0 No Details →
1.12.0 18 Apr 2024 H3 M1 U4 Apache-2.0 No Details →
1.11.0 30 Jan 2024 H3 M1 U4 Apache-2.0 No Details →
1.10.1 04 Jan 2024 H3 M3 U6 Apache-2.0 No Details →
1.10.0.post0 08 Dec 2023 H3 M4 U7 Apache-2.0 No Details →
1.10.0 01 Dec 2023 H3 M4 U7 Apache-2.0 No Details →
1.9.2.post0 08 Nov 2023 H3 M4 U7 Apache-2.0 No Details →
1.9.2 07 Nov 2023 H4 M4 U7 Apache-2.0 No Details →
1.9.1.post0 13 Oct 2023 H5 M4 U9 Apache-2.0 No Details →
1.9.1 10 Oct 2023 H5 M4 U9 Apache-2.0 No Details →
1.9.0 27 Sep 2023 H5 M4 U9 Apache-2.0 No Details →
1.8.2.post1 21 Sep 2023 H5 M4 U9 Apache-2.0 No Details →
1.8.2.post0 15 Sep 2023 H5 M4 U9 Apache-2.0 No Details →
1.8.2 29 Aug 2023 H5 M4 U9 Apache-2.0 No Details →
1.8.1 02 Aug 2023 C1 H5 M4 U10 Apache-2.0 No Details →
1.8.0 05 Jun 2023 C1 H5 M4 U10 Apache-2.0 No Details →
1.7.3 19 Apr 2023 C1 H5 M4 U10 Apache-2.0 No Details →
1.7.2 20 Mar 2023 C1 H5 M4 U10 Apache-2.0 No Details →
1.7.1 27 Jan 2023 C1 H6 M4 U10 Apache-2.0 No Details →
1.7.0 15 Dec 2022 C1 H6 M4 U10 Apache-2.0 No Details →
1.6.0 27 Sep 2022 C1 H6 M4 U10 Apache-2.0 No Details →
1.5.0.post0 13 Jul 2022 C1 H7 M4 U10 Apache-2.0 No Details →
1.5.0 16 Jun 2022 C1 H7 M4 U11 Apache-2.0 No Details →
1.4.1.post1 12 Feb 2022 C1 H7 M4 U11 Apache-2.0 No Details →
1.4.1.post0 11 Feb 2022 C1 H7 M4 U11 Apache-2.0 No Details →
1.4.1 11 Feb 2022 C1 H7 M4 U11 Apache-2.0 No Details →
1.4.0 19 Nov 2021 C1 H7 M4 U9 Apache-2.0 No Details →
1.3.0.post1 18 Oct 2021 C1 H7 M4 U9 Apache-2.0 No Details →
1.3.0.post0 18 Sep 2021 C1 H7 M4 U9 non-standard No Details →
1.3.0 17 Sep 2021 C1 H7 M4 U9 non-standard No Details →
1.2.0 18 Aug 2021 C1 H7 M4 U9 Apache-2.0 No Details →
1.1.1 13 Aug 2021 C1 H7 M4 U11 non-standard No Details →
1.1.0 30 Jun 2021 C1 H7 M4 U11 non-standard No Details →
1.1.0rc0 30 Jun 2021 C1 H7 M4 U11 non-standard No Details →
1.0.2.post0 14 Jun 2021 C1 H7 M4 U11 MIT No Details →
1.0.2 19 May 2021 C1 H7 M4 U11 MIT No Details →
1.0.1 05 Apr 2021 C1 H7 M4 U11 MIT No Details →
0.9.1.post2 26 Mar 2021 C1 H7 M4 U11 MIT No Details →
1.0.0.post3 22 Mar 2021 C1 H7 M4 U11 MIT No Details →
1.0.0.post2 19 Mar 2021 C1 H7 M4 U11 MIT No Details →
1.0.0.post1 19 Mar 2021 C1 H7 M4 U11 MIT No Details →
1.0.0.post0 18 Mar 2021 C1 H7 M4 U11 MIT No Details →
1.0.0 16 Mar 2021 C1 H7 M4 U11 MIT No Details →
0.9.1.post1 18 Feb 2021 C1 H7 M4 U11 MIT No Details →
0.9.1.post0 17 Feb 2021 C1 H7 M4 U11 MIT No Details →
0.9.1 16 Feb 2021 C1 H7 M4 U11 MIT No Details →
0.9.0.post5 25 Jan 2021 C1 H7 M4 U11 MIT No Details →
0.9.0 18 Jan 2021 C1 H7 M4 U11 MIT No Details →
0.9.0.post4 18 Jan 2021 C1 H7 M4 U11 MIT No Details →
0.9.0.post3 15 Jan 2021 C1 H7 M4 U11 MIT No Details →
0.9.0.post2 14 Jan 2021 C1 H7 M4 U11 MIT No Details →
0.8.2.post0 15 Dec 2020 C1 H7 M4 U11 MIT No Details →
0.8.2 01 Dec 2020 C1 H7 M4 U11 MIT No Details →
0.8.1.post0 30 Nov 2020 C1 H7 M4 U11 MIT No Details →
0.8.1 20 Nov 2020 C1 H7 M4 U11 MIT No Details →
0.8.0.post0 06 Nov 2020 C1 H7 M4 U11 MIT No Details →
0.8.0 27 Oct 2020 C1 H7 M4 U11 MIT No Details →
0.7.5.post2 15 Oct 2020 C1 H7 M4 U11 MIT No Details →
0.7.5.post1 14 Oct 2020 C1 H7 M4 U11 MIT No Details →
0.7.4.post1 08 Oct 2020 C1 H7 M4 U11 MIT No Details →
0.7.4.post0 17 Aug 2020 C1 H7 M4 U11 MIT No Details →
0.7.4 13 Aug 2020 C1 H7 M4 U11 MIT No Details →
0.7.3 09 Jul 2020 C1 H7 M4 U11 MIT No Details →
0.7.2 11 Jun 2020 C1 H7 M4 U11 MIT No Details →
0.7.1 05 Jun 2020 C1 H7 M4 U11 MIT No Details →
0.7.0 29 May 2020 C1 H7 M4 U11 MIT No Details →
0.6.1 18 May 2020 C1 H7 M4 U11 MIT No Details →
0.6.0 08 May 2020 C1 H7 M4 U11 MIT No Details →
0.5.1 30 Mar 2020 C1 H7 M4 U11 MIT No Details →
0.5.0 11 Mar 2020 C1 H7 M4 U11 MIT No Details →
0.4.8 26 Feb 2020 C1 H7 M4 U11 MIT No Details →
0.4.7 25 Feb 2020 C1 H7 M4 U11 MIT No Details →
0.4.6.post2 12 Feb 2020 C1 H7 M4 U11 MIT No Details →
0.4.6.post1 07 Feb 2020 C1 H7 M4 U11 MIT No Details →
0.4.6 07 Feb 2020 C1 H7 M4 U11 MIT No Details →
0.4.5 29 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.4.post2 23 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.4.post1 22 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.4 22 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.3 16 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.2 12 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.4.1 10 Jan 2020 C1 H7 M4 U11 MIT No Details →
0.7.5 — C1 H7 M4 U9 MIT No Details →
0.7.5.post0 — C1 H7 M4 U9 MIT No Details →
0.9.0.post3-1 — C1 H7 M4 U9 — No Details →

All 101 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 5
  • 2024 8
  • 2025 4
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 23 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for label-studio

The 5 most severe of 23 vulnerabilities recorded for this package

Search all 23 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-43791: Label Studio Hardcoded Django SECRET_KEY Vulnerability 9.8 critical 1.8.2 09 Nov 2023
CVE-2023-43791: Label Studio Privilege Escalation Vulnerability 8.8 high 3d06c5131c15600621e08b06f07d976887cde81b 09 Nov 2023
CVE-2025-25297: Label Studio SSRF Vulnerability in S3 Storage Endpoint 8.6 high 1.16.0 07 Jul 2026
CVE-2026-22033: Label Studio Full Account Takeover via Chained Stored XSS and IDOR 8.6 high No fix published 07 Jul 2026
CVE-2026-22033: Label Studio Full Account Takeover via Chained Stored XSS and IDOR 8.6 high No fix published 12 Jan 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About label-studio

Is label-studio safe to use?

Vulert records 23 vulnerabilities for label-studio in PyPI: 1 critical, 7 high, 4 medium and 0 low, plus 11 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is label-studio's Vulert package health score?

Vulert scores label-studio 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of label-studio affected?

Yes. 1.23.2, the version you would install today, has 5 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of label-studio should I use?

1.23.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does label-studio have?

23 vulnerabilities are recorded for label-studio in the PyPI ecosystem: 1 critical, 7 high, 4 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new label-studio vulnerabilities disclosed?

4 vulnerabilities were recorded for label-studio in the last 12 months, and the oldest entry in this database dates to 03 Oct 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of label-studio are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor label-studio for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the label-studio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.