# CVE-2026-85179: Label Studio through 1.23.0 SSRF via Unvalidated Webhook URL

> Authenticated users can exploit unvalidated webhook URLs to access internal services and exfiltrate annotation data via Server-Side Request Forgery.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-93hf-p7mp-qw5g, MINI-f7x4-ch3v-83x6

## What is CVE-2026-85179?

CVE-2026-85179 is a high-severity server-side request forgery vulnerability in HumanSignal label-studio, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Label Studio through 1.23.0 fails to validate webhook URLs, allowing authenticated users to dispatch requests to internal services including RFC 1918 addresses and cloud metadata endpoints. Attackers can create webhooks targeting private networks and exfiltrate annotation data by enabling payload transmission in outbound requests.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-85179?


## How do I fix CVE-2026-85179?

Apply the vendor's patch.

## Is CVE-2026-85179 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85179 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85179 and fix it if it is affected.

What it is: CVE-2026-85179 is a high-severity server-side request forgery vulnerability in HumanSignal label-studio, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85179 exists.

Affected product: HumanSignal label-studio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85179/ (Markdown: https://insights.sbomify.com/CVE-2026-85179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85179
- OSV: https://osv.dev/vulnerability/CVE-2026-85179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85179/
Summaries are generated and may contain mistakes; the official description above is the record.