CVE-2025-25297: Label studio Label Studio Allows Server-Side Request Vulnerability

HIGH
Advisory Identifier: GHSA-m238-fmcw-wh58
CVSS 8.6
CWE-918
Published
Advisory Summary

CVE-2025-25297 is a HIGH (CVSS 8.6) label studio allows server-side request vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Label studio libraries in the PyPI ecosystem. The issue involves label studio allows server-side request forgery in the s3 storage endpoint. Remediation is available by upgrading affected packages to version 1.16.0.

CVE-2025-25297 at a Glance

CVE Identifier CVE-2025-25297
GHSA Identifier GHSA-m238-fmcw-wh58
Severity HIGH
CVSS v3.1 Base Score 8.6
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Label studio
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 8.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-25297

To remediate this vulnerability, upgrade all affected Label studio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

label-studio fixed: 1.16.0
pip install label-studio>=1.16.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show label-studio

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2025-25297, inspect your installed packages using pip:

pip show label-studio

Analyze the terminal output to locate any version of Label studio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.16.0), your application is affected.

Note: The pip show label-studio command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Label studio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Description Label Studio's S3 storage integration feature contains a Server-Side Request Forgery (SSRF) vulnerability in its endpoint configuration. When creating an S3 storage connection, the application allows users to specify a custom S3 endpoint URL via the s3_endpoint parameter. This endpoint URL is passed directly to the boto3 AWS SDK without proper validation or restrictions on the protocol or destination. The vulnerability allows an attacker to make the application send HTTP requests to arbitrary internal services by specifying them as the S3 endpoint. When the storage sync operation is triggered, the application attempts to make S3 API calls to the specified endpoint, effectively making HTTP requests to the target service and returning the response in error messages. This SSRF vulnerability enables attackers to bypass network segmentation and access internal services that should not be accessible from the external network. The vulnerability is particularly severe because error messages from failed requests contain the full response body, allowing data exfiltration from internal services. ## Steps to reproduce 1. Create an account in Label Studio 2. Create a new project with basic configuration 3. Create an S3 storage connection with the following configuration: ```json { "project": 1, "title": "Test Storage", "bucket": "<filename>", "s3_endpoint": "http://internal-web", "use_blob_urls": true, "aws_access_key_id": "test", "aws_secret_access_key": "test" } ``` 4. Trigger a storage sync operation by sending a POST request to `/api/storages/s3/[storage_id]/sync` The application will attempt to connect to the specified endpoint URL as if it were an S3 service. When the request fails due to invalid S3 API responses, the error message will contain the raw response from the internal service, allowing access to internal resources. ## Mitigations - Implement strict validation of S3 endpoint URLs to allow only valid S3service endpoints - Add an allowlist of endpoint domains and protocols - Sanitize error messages to prevent leakage of sensitive information from failed requests - Consider implementing network-level controls to restrict outbound connections from the application server ## Impact This vulnerability has high severity as it allows authenticated users to make requests to arbitrary internal services from the application server, potentially exposing sensitive internal resources and bypassing network segmentation. The inclusion of response data in error messages makes this particularly effective for data exfiltration.

CVE-2025-25297 Affected Label studio Versions

1 component(s)
Fixed Versions:
1.16.0
Product / Package Ecosystem Affected Versions Fixed Version
label-studio
PyPI
< 1.16.0
1.16.0

References

Frequently Asked Questions

What is CVE-2025-25297?
CVE-2025-25297 is a security vulnerability in Label studio involving Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint under CWE-918: Server-Side Request Forgery (SSRF).
Which Label studio versions are affected?
Affected versions include releases prior to 1.16.0 across affected packages: label-studio.
What version fixes CVE-2025-25297?
Upgrading to 1.16.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is label-studio affected?
Yes, label-studio is affected in releases prior to 1.16.0. Upgrade your dependency to 1.16.0 or later.
What is the CVSS score of CVE-2025-25297?
CVE-2025-25297 has a CVSS v3.1 base score of 8.6 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N.
What CWE is associated with CVE-2025-25297?
CVE-2025-25297 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check PyPI dependencies for CVE-2025-25297?
Run the dependency tree command: 'pip show label-studio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-m238-fmcw-wh58",
  "modified" : "2025-02-14T22:18:10Z",
  "published" : "2025-02-14T15:26:56Z",
  "aliases" : [ "CVE-2025-25297" ],
  "summary" : "Label Studio allows Server-Side Request Forgery in the S3 Storage Endpoint",
  "details" : "## Description\nLabel Studio's S3 storage integration feature contains a Server-Side Request Forgery (SSRF) vulnerability in its endpoint configuration. When creating an S3 storage connection, the application allows users to specify a custom S3 endpoint URL via the s3_endpoint parameter. This endpoint URL is passed directly to the boto3 AWS SDK without proper validation or restrictions on the protocol or destination.\n\nThe vulnerability allows an attacker to make the application send HTTP requests to arbitrary internal services by specifying them as the S3 endpoint. When the storage sync operation is triggered, the application attempts to make S3 API calls to the specified endpoint, effectively making HTTP requests to the target service and returning the response in error messages.\n\nThis SSRF vulnerability enables attackers to bypass network segmentation and access internal services that should not be accessible from the external network. The vulnerability is particularly severe because error messages from failed requests contain the full response body, allowing data exfiltration from internal services.\n\n## Steps to reproduce\n1. Create an account in Label Studio\n\n2. Create a new project with basic configuration\n\n3. Create an S3 storage connection with the following configuration:\n   ```json\n   {\n     \"project\": 1,\n     \"title\": \"Test Storage\",\n     \"bucket\": \"<filename>\",\n     \"s3_endpoint\": \"http://internal-web\",\n     \"use_blob_urls\": true,\n     \"aws_access_key_id\": \"test\",\n     \"aws_secret_access_key\": \"test\"\n   }\n   ```\n4. Trigger a storage sync operation by sending a POST request to `/api/storages/s3/[storage_id]/sync`\n\nThe application will attempt to connect to the specified endpoint URL as if it were an S3 service. When the request fails due to invalid S3 API responses, the error message will contain the raw response from the internal service, allowing access to internal resources.\n   \n## Mitigations\n- Implement strict validation of S3 endpoint URLs to allow only valid S3service endpoints\n- Add an allowlist of endpoint domains and protocols\n- Sanitize error messages to prevent leakage of sensitive information from failed requests\n- Consider implementing network-level controls to restrict outbound connections from the application server\n\n## Impact\nThis vulnerability has high severity as it allows authenticated users to make requests to arbitrary internal services from the application server, potentially exposing sensitive internal resources and bypassing network segmentation. The inclusion of response data in error messages makes this particularly effective for data exfiltration.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "label-studio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.16.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/HumanSignal/label-studio/security/advisories/GHSA-m238-fmcw-wh58"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-25297"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/HumanSignal/label-studio/commit/06a2b29c1208e1878ccae66e6b84c8b24598fa79"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/HumanSignal/label-studio"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-02-14T15:26:56Z",
    "nvd_published_at" : "2025-02-14T20:15:36Z"
  }
}