fohrloop dash-uploader up to 0.1.0/0.7.0a2 httprequesthandler.py Upload max_file_size unrestricted upload

Summaryinfo

A vulnerability marked as critical has been reported in fohrloop dash-uploader up to 0.1.0/0.7.0a2. This issue affects the function Upload of the file dash_uploader/httprequesthandler.py. Performing a manipulation of the argument max_file_size results in unrestricted upload. This vulnerability is cataloged as CVE-2026-38361. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, was found in fohrloop dash-uploader up to 0.1.0/0.7.0a2. This affects the function Upload of the file dash_uploader/httprequesthandler.py. The manipulation of the argument max_file_size with an unknown input leads to a unrestricted upload vulnerability. CWE is classifying the issue as CWE-434. The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Multiple unauthenticated denial-of-service (DoS) issues in fohrloop dash-uploader v0.1.0 through v0.7.0a2. The chunked-upload handler (dash_uploader/httprequesthandler.py, dash_uploader/upload.py) trusts unsanitized, attacker-controlled upload parameters (e.g. flowTotalChunks) and does not enforce the documented max_file_size limit, allowing a remote, unauthenticated attacker to cause an out-of-memory (OOM) process crash (unbounded range(1, flowTotalChunks + 1) allocation), truncation of the target file to zero bytes (flowTotalChunks=0, where the all([]) == True quirk runs the file-assembly branch on zero chunks), permanent disk exhaustion (never-cleaned-up temporary directories per flowIdentifier), and a complete bypass of the documented max_file_size limit.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-38361 since 04/06/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/10/2026). MITRE ATT&CK project uses the attack technique T1608.002 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• fohrloop

Name

• dash-uploader

Version

• 0.1.0
• 0.7.0a2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion