# CVE-2026-34981: whisperX REST API: SSRF in download_from_url() — URL validation happens after HTTP request, extension bypass via .mp3

> An unauthenticated attacker can trigger Server-Side Request Forgery in whisperX by bypassing URL validation, potentially accessing internal resources.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-6rc7-r867-c635

## What is CVE-2026-34981?

CVE-2026-34981 is a medium-severity server-side request forgery vulnerability in pavelzbornik whisperX-FastAPI, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The whisperX API is a tool for enhancing and analyzing audio content. From 0.3.1 to 0.5.0, FileService.download_from_url() in app/services/file_service.py calls requests.get(url) with zero URL validation. The file extension check occurs AFTER the HTTP request is already made, and can be bypassed by appending .mp3 to any internal URL. The /speech-to-text-url endpoint is unauthenticated. This vulnerability is fixed in 0.6.0.

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

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

It affects 1 product.


Products: Pavelzbornik Whisperx Rest Api.

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

No fix has been published for CVE-2026-34981 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-34981 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34981 is a medium-severity server-side request forgery vulnerability in pavelzbornik whisperX-FastAPI, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34981 exists.

Affected product: pavelzbornik whisperX-FastAPI. 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-34981/ (Markdown: https://insights.sbomify.com/CVE-2026-34981/index.md)
```

## Sources

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

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