CVE-2022-36551

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 9.2%, top 7% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 5%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A Server Side Request Forgery (SSRF) in the Data Import module in Heartex - Label Studio Community Edition versions 1.5.0 and earlier allows an authenticated user to access arbitrary files on the system. Furthermore, self-registration is enabled by default in these versions of Label Studio enabling a remote attacker to create a new account and then exploit the SSRF.

CVSS v3
6.5
EG Score
6.5(medium)
EPSS
91.4%
KEV
Not listed

Published

October 3, 2022

Last Modified

July 9, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

fix: DEV-3212: Add validation to avoid users import local files using URL

Fix merged in heartexlabs/label-studio PR #2840 on 2022-08-23 — awaiting tagged release

https://github.com/heartexlabs/label-studio/pull/2840
generic

Open Source Data Labeling and AI Evaluation | Label Studio

http://labelstud.io
generic

Scale Human Judgment. Build Better AI. | HumanSignal

http://heartex.com

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
label-studio0.4.0rc1 ... 1.5.0rc9 (155 versions)1.5.0.post0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:44 UTCEPSS rescore
  2. 2026-07-12 05:44 UTCEPSS rescore
  3. 2026-07-11 08:25 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-09 02:56 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  6. 2026-07-09 01:31 UTCMITRE cvelistV5
  7. 2026-07-08 15:12 UTCEPSS rescore
  8. 2026-07-06 16:25 UTCEPSS rescore
  9. 2026-07-06 16:25 UTCEPSS rescore
  10. 2026-07-06 02:21 UTCEPSS rescore
  11. 2026-07-06 02:21 UTCEPSS rescore
  12. 2026-07-05 02:28 UTCEPSS rescore
  13. 2026-07-05 02:26 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  14. 2026-07-05 02:26 UTCMITRE cvelistV5
  15. 2026-07-04 06:29 UTCEPSS rescore
  16. 2026-07-04 06:29 UTCEPSS rescore
  17. 2026-07-01 15:04 UTCEPSS rescore
  18. 2026-06-30 23:20 UTCEPSS rescore
  19. 2026-06-30 23:20 UTCEPSS rescore
  20. 2026-06-29 14:04 UTCEPSS rescore
  21. 2026-06-28 17:02 UTCOSV refresh
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:54 UTCEPSS rescore
  24. 2026-06-28 04:54 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
Show 63 more
  1. 2026-06-27 03:07 UTCEPSS rescore
  2. 2026-06-25 13:48 UTCEPSS rescore
  3. 2026-06-25 13:48 UTCEPSS rescore
  4. 2026-06-24 14:03 UTCEPSS rescore
  5. 2026-06-24 14:03 UTCEPSS rescore
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-22 14:24 UTCEPSS rescore
  9. 2026-06-22 14:24 UTCEPSS rescore
  10. 2026-06-21 14:55 UTCEPSS rescore
  11. 2026-06-21 14:55 UTCEPSS rescore
  12. 2026-06-21 01:58 UTCEPSS rescore
  13. 2026-06-21 01:58 UTCEPSS rescore
  14. 2026-06-19 19:24 UTCEPSS rescore
  15. 2026-06-19 19:24 UTCEPSS rescore
  16. 2026-06-18 17:51 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-17 17:51 UTCEPSS rescore
  19. 2026-06-17 17:51 UTCEPSS rescore
  20. 2026-06-16 17:51 UTCEPSS rescore
  21. 2026-06-15 17:46 UTCEPSS rescore
  22. 2026-06-14 23:15 UTCEPSS rescore
  23. 2026-06-13 22:58 UTCEPSS rescore
  24. 2026-06-12 23:10 UTCEPSS rescore
  25. 2026-06-12 23:10 UTCEPSS rescore
  26. 2026-06-11 13:58 UTCEPSS rescore
  27. 2026-06-11 13:58 UTCEPSS rescore
  28. 2026-06-11 08:09 UTCOSV refresh
  29. 2026-06-10 22:17 UTCEPSS rescore
  30. 2026-06-10 13:20 UTCEPSS rescore
  31. 2026-06-08 14:15 UTCEPSS rescore
  32. 2026-06-08 14:15 UTCEPSS rescore
  33. 2026-06-07 15:23 UTCEPSS rescore
  34. 2026-06-07 15:23 UTCEPSS rescore
  35. 2026-06-06 13:46 UTCEPSS rescore
  36. 2026-06-06 13:46 UTCEPSS rescore
  37. 2026-06-06 13:46 UTCEPSS rescore
  38. 2026-06-05 22:46 UTCEPSS rescore
  39. 2026-06-05 22:45 UTCEPSS rescore
  40. 2026-06-05 06:09 UTCEPSS rescore
  41. 2026-06-05 06:09 UTCEPSS rescore
  42. 2026-06-04 13:11 UTCEPSS rescore
  43. 2026-06-04 13:11 UTCEPSS rescore
  44. 2026-06-02 20:11 UTCEPSS rescore
  45. 2026-06-02 20:11 UTCEPSS rescore
  46. 2026-05-31 22:29 UTCEPSS rescore
  47. 2026-05-31 22:29 UTCEPSS rescore
  48. 2026-05-31 22:29 UTCEPSS rescore
  49. 2026-05-31 00:15 UTCEPSS rescore
  50. 2026-05-31 00:15 UTCEPSS rescore
  51. 2026-05-29 13:43 UTCEPSS rescore
  52. 2026-05-29 13:43 UTCEPSS rescore
  53. 2026-05-28 13:43 UTCEPSS rescore
  54. 2026-05-28 13:43 UTCEPSS rescore
  55. 2026-05-27 13:39 UTCEPSS rescore
  56. 2026-05-27 13:39 UTCEPSS rescore
  57. 2026-05-26 13:43 UTCEPSS rescore
  58. 2026-05-26 13:43 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore
  60. 2026-05-26 07:17 UTCEPSS rescore
  61. 2026-05-26 07:17 UTCEPSS rescore
  62. 2026-05-25 14:23 UTCEG score recompute
  63. 2026-05-24 16:51 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-51109
    First seen Mar 28, 2023

    Label Studio 1.5.0 - Authenticated Server Side Request Forgery (SSRF)

    Open source ↗

Frequently asked(5)

What is CVE-2022-36551?
CVE-2022-36551 is a medium vulnerability published on October 3, 2022. A Server Side Request Forgery (SSRF) in the Data Import module in Heartex - Label Studio Community Edition versions 1.5.0 and earlier allows an authenticated user to access arbitrary files on the system. Furthermore, self-registration is enabled by default in these versions of Label Studio enabling…
When was CVE-2022-36551 disclosed?
CVE-2022-36551 was first published in the National Vulnerability Database on October 3, 2022, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-36551 actively exploited?
CVE-2022-36551 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-36551?
CVE-2022-36551 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2022-36551?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-36551, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-36551

Explore →

Is Your Infrastructure Affected by CVE-2022-36551?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs