Security readout for executives and security teams
Plain-English summary
Label Studio versions 1.22.0 and earlier have a stored XSS issue in user profile custom_hotkeys. If abused, malicious JavaScript can run in other users’ browsers and may access or reset API tokens. The reported impact is full account takeover and unauthorized API access for affected Label Studio deployments.
Executive priority
Treat as a high-priority application security update if Label Studio is used for sensitive data labeling or internal ML workflows. The business risk is account takeover and unauthorized API access, not just browser nuisance.
Technical view
The CVE describes persistent XSS in custom_hotkeys, rendered through templates/base.html, combined with token exposure and insufficient CSRF protection on some API endpoints. An authenticated attacker, or a user induced to save malicious hotkeys, can trigger browser-side actions against victims. CVSS v4.0 is 8.6 high, with high confidentiality and integrity impact.
Likely exposure
Organizations running HumanSignal Label Studio 1.22.0 or earlier are in scope. Exposure is higher where many users share projects, administrators use the interface, or the application is reachable by untrusted authenticated users.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Abuse requires authentication or social engineering to modify custom_hotkeys, then victim page loads. The impact can extend to API token theft or reset, enabling account takeover.
Researcher notes
Evidence is based on the CVE record and GitHub advisory, PR, and commit references. The bundle names affected versions but does not provide a specific fixed version. Avoid assuming exploitation in the wild without KEV or vendor confirmation.
Mitigation direction
- Review the GitHub security advisory and vendor guidance for the fixed release path.
- Upgrade affected Label Studio deployments when a vendor-fixed version is available.
- Review PR 9084 and commit ea2462b for the vendor’s code-level remediation context.
- After remediation, rotate exposed or potentially exposed API tokens.
- Limit access to Label Studio to trusted users until remediation is complete.
Validation and detection
- Inventory Label Studio deployments and identify versions 1.22.0 or earlier.
- Check whether custom_hotkeys is enabled or populated in user profiles.
- Inspect custom_hotkeys values for unexpected script-like or HTML content.
- Confirm patched builds no longer render custom_hotkeys as executable browser content.
- Review application logs for unusual token access or token reset activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-22033 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.6 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.6HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/HumanSignal/label-studio/security/advisories/GHSA-2mq9-hm29-8qchCVE reference · x_refsource_CONFIRM
- https://github.com/HumanSignal/label-studio/pull/9084CVE reference · x_refsource_MISC
- https://github.com/HumanSignal/label-studio/commit/ea2462bf042bbf370b79445d02a205fbe547b505CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.