dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-44647

HIGH · 7.1 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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
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.

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 · high confidence

OneDev versions prior to 15.0.2 contain a path traversal vulnerability in LFS (Git Large File Storage) handling. Users with push permissions to any repository can manipulate LFS metadata to direct raw blob reads to arbitrary local filesystem paths accessible by the OneDev server process, enabling disclosure of sensitive server-side files.

MitigationUpgrade OneDev to version 15.0.2 or later. As an immediate workfallback, restrict push permissions to only trusted users and consider running OneDev in a sandboxed container with minimal filesystem permissions.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 OneDev installation and version
    Check the OneDev server version by accessing the web UI (usually at /~my) or checking the installation directory for a version file. Common installation paths include /opt/onedev, /home/onedev, or the directory where OneDev was installed. Run 'java -jar onedev*.jar --version' if you have CLI access.
    Affected if The installed version is lower than 15.0.2 (e.g., 15.0.1, 14.x, 13.x, etc.)
  2. Verify LFS is in use
    Check if Git LFS is enabled in any repository by inspecting .gitattributes files for 'filter=lfs' entries, or by listing .git/lfs/objects directories. In the OneDev web UI, navigate to a repository's settings and look for LFS configuration under 'Git LFS' settings.
    Affected if LFS is enabled and used in any repository on the server
  3. Audit push permission holders
    In OneDev web UI, review which users have push permissions: go to each project's 'Settings' > 'Roles' and check which users/groups are assigned roles with push or admin permissions. Alternatively, check the OneDev database or configuration for user-role mappings.
    Affected if Any user account other than strict administrators has push permissions to repositories

You are affected if OneDev version is below 15.0.2 AND LFS is enabled on the server AND untrusted users have push permissions to any repository.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OneDev to version 15.0.2 or later. As an immediate workfallback, restrict push permissions to only trusted users and consider running OneDev in a sandboxed container with minimal filesystem permissions.

Recommended fix High confidence

15.0.2

  1. Identify the current OneDev version running in your environment
  2. Review the OneDev 15.0.2 release notes for any migration requirements or注意事项
  3. Create a full backup of your OneDev instance including database and configuration
  4. Stop the OneDev service
  5. Upgrade OneDev to version 15.0.2 or later using your deployment method (Docker, JAR, or other)
  6. Verify the upgrade was successful by checking the version number in the UI or CLI
  7. Restart the OneDev service
  8. Test that Git LFS functionality works correctly after upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44647 — 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-44647 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