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

High 8.6 Published Updated

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

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

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, CWE-284

Which versions are affected by CVE-2026-22033?

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

PackageAffectedFixed in
label-studio PyPIAll versions to 1.22.0None
label-studio PyPIAll versions to 1.22.0None
label-studio PyPIAll versions to 1.22.0None

Products include 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.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-22033 being exploited?

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

Sources

Also known as GHSA-2mq9-hm29-8qch, PYSEC-2026-1502.

Is CVE-2026-22033 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free