Path Traversal in OneDev (CVE-2026-44647)
Summary
Path traversal in OneDev (CVE-2026-44647). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 15.0.2 or later.
Original description
The description as published by the source.
OneDev is a Git server with CI/CD, kanban, and packages. Prior to 15.0.2, there is behavior that breaks the expected boundary between repository-controlled LFS metadata and server-local filesystem paths. A repository object can steer raw blob reads to arbitrary local files that the server account can access. User with push permission to any repository will be able to access any server files accessible by server process. This vulnerability is fixed in 15.0.2.
Source: NIST National Vulnerability Database NVD
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-44647 has been found in OneDev.
Risk of unauthorized operations or information disclosure.
What to do: upgrade OneDev to 15.0.2 or later.
If unsure, ask your IT team or search "OneDev CVE-2026-44647" on the vendor's site.
CVE-2026-44647 (OneDev) — CWE-22
Patched: 15.0.2 — 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.
Path traversal (CWE-22) exists in OneDev.
Check the vendor advisory for the affected versions of OneDev.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 15.0.2.
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 'OneDev' . 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 'OneDev' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OneDevを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade OneDev to 15.0.2ステージング環境で 15.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。