dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-38360

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Directory Traversal vulnerability in fohrloop dash-uploader v.0.1.0 through v.0.7.0a2 allows a remote attacker to execute arbitrary code via the dash_uploader/httprequesthandler.py, BaseHttpRequestHandler.get_temp_root(), BaseHttpRequestHandler._post() components.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A directory traversal vulnerability in fohrloop dash-uploader versions 0.1.0 through 0.7.0a2 allows remote attackers to escape the intended directory boundaries via the get_temp_root() and _post() methods in dash_uploader/httprequesthandler.py, potentially leading to arbitrary code execution.

MitigationUpgrade to a patched version if available; otherwise, implement strict input validation on path parameters to reject directory traversal sequences (e.g., ../) and restrict file operations to whitelisted directories.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if dash-uploader is installed
    Run 'pip show dash-uploader' or check your Python environment's installed packages list for 'dash-uploader'
    Affected if dash-uploader package is present in the environment
  2. Determine the installed version
    Run 'pip show dash-uploader' and note the Version field, or check your requirements.txt/pipfile for the dash-uploader version
    Affected if The installed version is 0.1.0, 0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.7.0a1, or 0.7.0a2 (any version from 0.1.0 through 0.7.0a2)
  3. Verify the vulnerable httprequesthandler.py exists
    Locate the dash_uploader package installation directory and confirm that httprequesthandler.py is present
    Affected if The file dash_uploader/httprequesthandler.py exists in the installed package
  4. Confirm the upload endpoint is network-accessible
    Check your application configuration and runtime to determine if the dash-uploader upload functionality is exposed over a network (not localhost-only)
    Affected if The upload endpoint is reachable from network clients, allowing remote attackers to send requests
  5. Check if path traversal input validation is implemented
    Review application code that handles file upload requests, specifically looking at how path parameters are processed before being used in file operations
    Affected if The application accepts user-supplied path parameters without rejecting directory traversal sequences like ../

A user is affected if dash-uploader version 0.1.0 through 0.7.0a2 is installed AND the upload endpoint is network-accessible AND path inputs are not validated to reject traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to a patched version if available; otherwise, implement strict input validation on path parameters to reject directory traversal sequences (e.g., ../) and restrict file operations to whitelisted directories.

Recommended fix High confidence

latest stable release beyond v.0.7.0a2

  1. 1. Identify the current installed version of fohrloop dash-uploader in your environment using: pip show dash-uploader or pip list | grep dash-uploader
  2. 2. If your version is between 0.1.0 and 0.7.0a2 (inclusive), the application is vulnerable
  3. 3. Upgrade to the latest available version of dash-uploader using: pip install --upgrade dash-uploader
  4. 4. Verify the upgrade was successful by checking the new version: pip show dash-uploader
  5. 5. Test that the application functionality remains intact after the upgrade
Caveat Review release notes between your current version and the new version for any breaking changes or deprecated functionality

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-38360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-38360 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data