Nginx alias path traversal allows unauthenticated attackers to read all files on /label_studio/core/

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The vulnerability resides on the Nginx config file: https://github.com/heartexlabs/label-studio/blob/53944e6bcede75ca5c102d655013f2e5238e85e6/deploy/default.conf#L119 The pattern on location /static indicates a popular misconfiguration on Nginx servers presented in 2018 originally by Orange Tsai. This vulnerability allows an attacker to use a single path traversal payload in the matched location to traverse one directory above. This vulnerability only happens due to the location /static directive not having a slash / at the end, the following code shows an example of a safe configuration: The vulnerability works because Nginx will think that /static../ is a directory that should also be aliased to the folder, allowing /static/../ to be reached. In Label Studio's case, this means all files on /labelstudio/core/ are exposed. Of course, this means that only Label Studio instances that were deployed using the default nginx files introducted at Mar 31, 2021. This is a very easy…

Published by the source

24 Mar 2023, 22:04 UTC

Last modified by the source

2 Sep 2026, 22:15 UTC

Source last checked

26 Oct 2026, 13:51 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cpmr-mw4j-99r7

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cpmr-mw4j-99r7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-cpmr-mw4j-99r7

Advisory: Nginx alias path traversal allows unauthenticated attackers to read all files on /label_studio/core/
IDs: GHSA-cpmr-mw4j-99r7
Record: https://patchnext.com/advisories/ghsa-cpmr-mw4j-99r7 (revision 2, source checked 26 Oct 2026, 13:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: label-studio 1.7.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI label-studio: affected <= 1.7.1; fixed in 1.7.2

## Suggested inspection (read-only)
- `python -m pip show label-studio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on label-studio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cpmr-mw4j-99r7 (OSV record GHSA-cpmr-mw4j-99r7 lists affected ranges: PyPI label-studio >=0 <1.7.2 (fixed))
- Verified: https://github.com/advisories/GHSA-cpmr-mw4j-99r7 (GitHub-reviewed advisory GHSA-cpmr-mw4j-99r7 lists affected ranges: PyPI label-studio >=0 <=1.7.1)

Commands are suggestions: review each one before running it.