# CVE-2026-22033: Label Studio vulnerable to full account takeover by chaining Stored XSS + IDOR in User Profile via custom_hotkeys field

> Authenticated attackers can inject JavaScript via custom hotkeys to steal API tokens and take over user accounts in Label Studio.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jan 2026
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-2mq9-hm29-8qch, PYSEC-2026-1502

## What is CVE-2026-22033?

CVE-2026-22033 is a high-severity cross-site scripting vulnerability in HumanSignal label-studio, published on 12 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Label Studio is a multi-type data labeling and annotation tool. In 1.22.0 and earlier, a persistent stored cross-site scripting (XSS) vulnerability exists in the custom_hotkeys functionality of the application. An authenticated attacker (or one who can trick a user/administrator into updating their custom_hotkeys) can inject JavaScript code that executes in other users’ browsers when those users load any page using the templates/base.html template. Because the application exposes an API token endpoint (/api/current-user/token) to the browser and lacks robust CSRF protection on some API endpoints, the injected script may fetch the victim’s API token or call token reset endpoints — enabling full account takeover and unauthorized API access.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-22033?

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 to 1.22.0 | None |
| `label-studio` | PyPI | All versions to 1.22.0 | None |
| `label-studio` | PyPI | All versions to 1.22.0 | None |

Products: Humansignal Label Studio.

## How do I fix CVE-2026-22033?

No fix has been published for CVE-2026-22033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22033 exists.

## Other vulnerabilities in HumanSignal label-studio

- [CVE-2023-43791](https://insights.sbomify.com/CVE-2023-43791/): Label Studio has Hardcoded Django `SECRET_KEY` that can be Abused to Forge Session Tokens (critical 9.8)
- [CVE-2025-25297](https://insights.sbomify.com/CVE-2025-25297/): Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint (high 8.6)
- [CVE-2025-47783](https://insights.sbomify.com/CVE-2025-47783/): label-studio vulnerable to Cross-Site Scripting (Reflected) via the label_config parameter. (high 7.6)
- [CVE-2023-47117](https://insights.sbomify.com/CVE-2023-47117/): Object Relational Mapper Leak Vulnerability in Filtering Task in Label Studio (high 7.5)
- [CVE-2023-47115](https://insights.sbomify.com/CVE-2023-47115/): Label Studio XSS Vulnerability on Avatar Upload (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22033 and fix it if it is affected.

What it is: CVE-2026-22033 is a high-severity cross-site scripting vulnerability in HumanSignal label-studio, published on 12 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22033 exists.

Affected packages and fixed versions:
- label-studio (PyPI): affected all versions up to 1.22.0; no fix listed
- label-studio (PyPI): affected all versions up to 1.22.0; no fix listed
- label-studio (PyPI): affected all versions up to 1.22.0; no fix listed

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-2026-22033/ (Markdown: https://insights.sbomify.com/CVE-2026-22033/index.md)
```

## Sources

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

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