# CVE-2022-36551: Heartex - Label Studio Community Edition vulnerable to SSRF in the Data Import module

> An authenticated user can exploit SSRF in Label Studio to access arbitrary system files, with remote exploitation possible due to default self-registration.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Oct 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-pc6f-259w-w3j6, PYSEC-2022-300

## What is CVE-2022-36551?

CVE-2022-36551 is a medium-severity server-side request forgery vulnerability in n/a, published on 3 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Server Side Request Forgery (SSRF) in the Data Import module in Heartex - Label Studio Community Edition versions 1.5.0 and earlier allows an authenticated user to access arbitrary files on the system. Furthermore, self-registration is enabled by default in these versions of Label Studio enabling a remote attacker to create a new account and then exploit the SSRF.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-36551?

3 open source packages ship an affected version, including label-studio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `label-studio` | PyPI | All versions | 1.5.0.post0 |
| `label-studio` | PyPI | All versions | 1.6.0 |
| `label-studio` | PyPI | All versions | 1.6.0 |

Products: Heartex Label Studio.

## How do I fix CVE-2022-36551?

Upgrade label-studio to a fixed version for your release line: 1.5.0.post0 or 1.6.0.

## Is CVE-2022-36551 being exploited?

There is no known exploitation of CVE-2022-36551 in the wild and no public exploit code.

Public exploit code:

- Label Studio 1.5.0 - Authenticated Server Side Request Forgery (SSRF) (exploitdb)
- Case study: Label Studio CVE-2022-36551 (task-import URL opened with urlopen). Demo only, not for use. (github_poc): https://github.com/ferralon-demo/label-studio-url-import-ssrf

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36551 and fix it if it is affected.

What it is: CVE-2022-36551 is a medium-severity server-side request forgery vulnerability in n/a, published on 3 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36551 in the wild and no public exploit code.

Affected packages and fixed versions:
- label-studio (PyPI): affected all versions; fixed in 1.5.0.post0
- label-studio (PyPI): affected all versions; fixed in 1.6.0
- label-studio (PyPI): affected all versions; fixed in 1.6.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-36551/ (Markdown: https://insights.sbomify.com/CVE-2022-36551/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-36551
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-36551
- OSV: https://osv.dev/vulnerability/CVE-2022-36551

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-36551/
Summaries are generated and may contain mistakes; the official description above is the record.
