Heartex - Label Studio Community Edition vulnerable to SSRF in the Data Import moduleGHSA-pc6f-259w-w3j6
MEDIUMFix: heartexlabs/label-studio#2840GHSA-pc6f-259w-w3j6 is a medium-severity (CVSS 6.5) Server-Side Request Forgery (SSRF) vulnerability in label-studio. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for label-studio — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
label-studioReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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. This issue is fixed in version 1.6.0.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | label-studio | all versions | 1.6.0pip install --upgrade 'label-studio==1.6.0' |
Affected Products
label studioheartexResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Label Studio 1.5.0 - Authenticated Server Side Request Forgery (SSRF)
by Ryan Smith · Mar 28, 2023
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for label-studio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update label-studio to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pc6f-259w-w3j6 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is GHSA-pc6f-259w-w3j6 in your dependencies?
Find it across PyPI, including transitive dependencies.