Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-22033

Vulnerability in label-studio (CVE-2026-22033)

Summary

vulnerability in label-studio (CVE-2026-22033). Risk of unauthorized operations or information disclosure. Exploitable via `PATCH /api/users/{id}/`.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-22033** has been found in label-studio. Attackers can target a specific entry point like `PATCH /api/users/{id}/` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: apply the vendor's official patched release. If unsure, ask your IT team or search "label-studio CVE-2026-22033" on the vendor's site.
CVE-2026-22033 (label-studio) — CWE-285 / Attack surface: PATCH /api/users/{id}/ / GET /user/login/ / GET /api/current-user/whoami / PATCH /api/users/25 Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-285) exists in label-studio. Attackers reach the vulnerable code path via `PATCH /api/users/{id}/` without authentication.
📍 Affected scope
label-studio — . Attack surface: PATCH /api/users/{id}/ / GET /user/login/ / GET /api/current-user/whoami / PATCH /api/users/25.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `PATCH /api/users/{id}/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'label-studio' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'label-studio' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `label-studio` を grep し、稼働しているサービス・バージョンを把握する。

  2. 3
    Hunt for indicators of compromise detect 
    grep 'PATCH /api/users/{id}/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで `PATCH /api/users/{id}/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 7
    Post-deployment verification verify 
    Replay attack against PATCH /api/users/{id}/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI label-studio
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.22.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →