Label Studio SSRF on Import Bypassing SSRF_PROTECTION_ENABLED Protections
CVE-2023-47116GHSA-p59w-9gqw-wj8r
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (label-studio 1.11.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI label-studio
- Affected
- < 1.11.0
- Fixed in
- 1.11.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-p59w-9gqw-wj8r lists affected ranges: PyPI label-studio >=0 <1.11.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-p59w-9gqw-wj8r lists affected ranges: PyPI label-studio >=0 <1.11.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2023-47116: 0.74% estimated exploitation activity in the next 30 days; percentile 54.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Introduction This write-up describes a vulnerability found in Label Studio, a popular open source data labeling tool. The vulnerability affects all versions of Label Studio prior to 1.11.0 and was tested on version 1.8.2. Overview Label Studio's SSRF protections that can be enabled by setting the SSRFPROTECTIONENABLED environment variable can be bypassed to access internal web servers. This is because the current SSRF validation is done by executing a single DNS lookup to verify that the IP address is not in an excluded subnet range. This protection can be bypassed by either using HTTP redirection or performing a DNS rebinding attack. Description The following tasksfromurl method in labelstudio/dataimport/uploader.py performs the SSRF validation (validateuploadurl) before sending the request. The validateuploadurl code in labelstudio/core/utils/io.py is shown below. The issue here is the SSRF validation is only performed before the request is sent, and does not validate the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-p59w-9gqw-wj8r
- Revision 1 · created ·
Published from osv record GHSA-p59w-9gqw-wj8r
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2023-47116 Advisory: Label Studio SSRF on Import Bypassing `SSRF_PROTECTION_ENABLED` Protections IDs: CVE-2023-47116, GHSA-p59w-9gqw-wj8r Record: https://patchnext.com/advisories/cve-2023-47116 (revision 2, source checked 26 Oct 2026, 13:27 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) 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.11.0. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI label-studio: affected < 1.11.0; fixed in 1.11.0 ## 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-p59w-9gqw-wj8r (OSV record GHSA-p59w-9gqw-wj8r lists affected ranges: PyPI label-studio >=0 <1.11.0 (fixed)) - Verified: https://github.com/advisories/GHSA-p59w-9gqw-wj8r (GitHub-reviewed advisory GHSA-p59w-9gqw-wj8r lists affected ranges: PyPI label-studio >=0 <1.11.0) Commands are suggestions: review each one before running it.
Loading voting…