CVE-2026-38360: Directory Traversal vulnerability in fohrloop dash-uploader v.0.1.0 through v.0.7.0a2 allows a remote attac...
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-38360 is a critical directory traversal issue in dash-uploader. A remote unauthenticated attacker may be able to abuse upload request handling to write outside intended temporary directories and potentially execute arbitrary code. Organizations using affected versions should treat exposed upload features as urgent until vendor guidance is confirmed.
Executive priority
Prioritize within emergency patch or compensating-control workflows for any internet-facing use. The risk is business-critical because the reported impact includes possible arbitrary code execution without authentication, but active exploitation is not confirmed in the provided sources.
Technical view
The CVE describes CWE-22 in fohrloop dash-uploader versions 0.1.0 through 0.7.0a2, involving httprequesthandler.py methods get_temp_root() and _post(). CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely in Python Dash applications that include dash-uploader and expose its upload handler to users or the internet. The bundle’s affected product metadata is incomplete, but the CVE description names dash-uploader versions 0.1.0 through 0.7.0a2.
Exploitation context
The provided data supports remote, unauthenticated exploitation potential based on CVSS and the CVE description. It does not show CISA KEV listing or another cited confirmation of active exploitation. A public CVE-specific GitHub reference exists, but the bundle does not establish real-world exploitation.
Researcher notes
The source bundle has a strong severity signal but incomplete product metadata and no confirmed patch statement. Focus research on version confirmation, handler exposure, and vendor advisory status. Avoid assuming exploit prevalence from the existence of a CVE-specific repository alone.
Mitigation direction
Inventory applications using dash-uploader versions 0.1.0 through 0.7.0a2.
Check the GitHub advisory, project issue, and PyPI page for vendor-approved fixes.
Disable or restrict exposed dash-uploader upload routes until remediation is confirmed.
Limit file-system permissions for application and upload temporary directories.
Monitor affected applications for unexpected file writes or process execution.
Validation and detection
Review dependency manifests and runtime packages for dash-uploader version use.
Map all public or authenticated routes that invoke dash-uploader upload handling.
Confirm whether upload endpoints are internet-accessible or reachable by untrusted users.
Review application logs for unusual upload paths, failed writes, or abnormal server errors.
Do not mark fixed until vendor guidance or a safe upgraded version is verified.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.