CVE-2026-72560 in Label Studio
Summary
by MITRE • 08/11/2026
A server-side request forgery vulnerability in HumanSignal Label Studio through 1.24.0.dev0 exists because SSRF_PROTECTION_ENABLED is set to false by default. The import-from-URL endpoint fetches any caller-supplied URL including internal loopback addresses on the default installation. An authenticated user can use this to reach internal services, cloud metadata endpoints, and other resources not intended for external access.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 08/11/2026
HumanSignal Label Studio versions up to 1.24.0.dev0 contain a critical server-side request forgery vulnerability that stems from insecure default configuration practices. The vulnerability manifests when the SSRF_PROTECTION_ENABLED parameter remains set to false during default installation, creating an exploitable path for authenticated users to perform unauthorized network requests. This flaw specifically affects the import-from-URL endpoint which indiscriminately processes any URL supplied by callers without proper validation or sanitization mechanisms. The default configuration essentially disables fundamental security protections that should prevent access to internal network resources and sensitive endpoints.
The technical implementation of this vulnerability allows an authenticated attacker to leverage the application's legitimate functionality to make requests to internal loopback addresses and other restricted network destinations. This occurs because the application lacks proper input validation and network boundary enforcement when processing external URLs through the import endpoint. The flaw enables access to internal services that typically reside behind firewalls or network segmentation controls, potentially exposing sensitive systems and data that should remain isolated from external access. Attackers can exploit this by crafting malicious URLs that target internal resources such as cloud metadata endpoints, database servers, or other internal applications.
The operational impact of this vulnerability extends beyond simple information disclosure to encompass potential system compromise and lateral movement within affected networks. An authenticated user with access to Label Studio can effectively use the application as a proxy to scan internal network spaces, enumerate services, and potentially gain access to sensitive resources that would normally be protected by network architecture controls. This represents a significant escalation of privileges since the attacker can leverage the application's legitimate authentication mechanisms to access resources that should only be reachable through proper authorization channels. The vulnerability essentially bypasses traditional network security controls by using the application as an intermediary for unauthorized network requests.
Security mitigations for this vulnerability should prioritize immediate configuration changes to enable SSRF protection by default, ensuring that the SSRF_PROTECTION_ENABLED parameter is set to true in all installations. Organizations must implement robust input validation mechanisms that filter and sanitize URL parameters before processing, rejecting any attempts to access loopback addresses, private network ranges, or internal services. Network segmentation controls should be enforced through proper firewall rules and access control lists to prevent applications from accessing internal resources even if the application itself is compromised. The vulnerability aligns with CWE-918 Server-Side Request Forgery and maps to ATT&CK technique T1071.004 Application Layer Protocol: DNS, where attackers use legitimate application functionality to bypass security controls. Regular security configuration reviews and automated scanning for insecure default settings should be implemented as part of comprehensive security operations to prevent similar issues in other applications.
This vulnerability demonstrates the critical importance of secure default configurations and proper input validation in web applications. The fact that protection mechanisms are disabled by default represents a fundamental security flaw that organizations must address through configuration management processes and security hardening procedures. The ease with which authenticated users can exploit this vulnerability highlights the need for comprehensive application security testing including security code reviews, penetration testing, and automated vulnerability scanning to identify and remediate similar issues before they can be exploited in production environments.