CVE-2026-34981

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-04-06 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-24 13:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 5.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-04-06 17:17 UTC

Last modified

2026-10-24 13:10 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-918 · Server-side request forgery

Record status

Analyzed

Affected

• Pavelzbornik Whisperx Rest Api < 0.6.0

Attack profile CVSS 3.1 · 5.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

Low

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-34981.md and follow it. Check whether this project is affected by CVE-2026-34981. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge