CVE-2026-22033: HumanSignal label-studio · Cross-site Scripting
Affects HumanSignal label-studioSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HumanSignallabel-studio | Affected
| Fixed in– |
GitHubhumansignal/label-studiopkg:github/humansignal/label-studioOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediately restrict access to the custom_hotkeys feature to trusted administrators only until a patch is available.
- Apply strict input validation and output encoding on all user-supplied data related to custom hotkeys to prevent script injection.
- Implement or enhance CSRF protections on all API endpoints, especially those handling authentication tokens and sensitive operations.
- Monitor and audit changes to custom hotkeys and API token usage for suspicious activity.
- Educate users and administrators about phishing and social engineering risks that could lead to malicious hotkey updates.
- Once HumanSignal releases a patched version, promptly upgrade to the fixed release.
- Consider isolating Label Studio instances in segmented network zones to limit lateral movement if compromise occurs.
- Employ Web Application Firewalls (WAFs) with rules to detect and block XSS payloads targeting Label Studio endpoints.
- Regularly review and rotate API tokens and credentials to minimize exposure windows.
- Conduct penetration testing and code reviews focused on input handling and authentication mechanisms.
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.