Vulnerability in dash-uploader (CVE-2026-38361)
Summary
Vulnerability in dash-uploader (CVE-2026-38361). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.7.0a1 or later.
Original description
The description as published by the source.
An issue 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, dash_uploader/upload.py in the Upload function and max_file_size parameter, dash_uploader/configure_upload.py components
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-38361 has been found in dash-uploader.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade dash-uploader to 0.7.0a1 or later.
If unsure, ask your IT team or search "dash-uploader CVE-2026-38361" on the vendor's site.
CVE-2026-38361 (dash-uploader) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.7.0a1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in dash-uploader.
Check the vendor advisory for the affected versions of dash-uploader.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 0.7.0a1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dash-uploader' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'dash-uploader' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dash-uploaderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dash-uploader to 0.7.0a1ステージング環境で 0.7.0a1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- exploit github.com
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org
- web nvd.nist.gov
- web pypi.org
- web cve@mitre.org
- web cve@mitre.org