CVE-2026-77763: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in juicedata juicefs
Description
The filestore backend in pkg/object/file.go, used for file:// stores and as a common juicefs sync destination, derived every operation's target from path(key), which returned either filepath.Join(d.root, key) or filepath.Clean(d.root + key) with no check that the result stayed beneath the root. Put, Get, Head, Delete, Chmod, Chown, Symlink and Readlink all consumed that value directly. Object keys enumerated from a source object store during a sync are not constrained the way local filesystem names are, so a key containing traversal segments causes juicefs to write attacker-supplied content to a path outside the intended local destination, and no error is returned. An operator syncing from a bucket whose contents they do not fully control, such as a shared or public bucket or one an attacker can write to, is therefore exposed to a file write at an attacker-influenced location. The fix changes path() to return an error and rejects any key whose resolved path escapes the root.
CVSS v3.1
Score 6.5medium
Affected software
juicedata
juicefs
pkg:golang/github.com/juicedata/juicefsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The filestore backend in juicefs (pkg/object/file.go) improperly limits pathname resolution when handling file operations such as Put, Get, Head, Delete, Chmod, Chown, Symlink, and Readlink. It constructs target paths by joining or cleaning the root directory with the object key but does not verify that the resulting path remains within the root directory. Object keys from source stores during sync can contain path traversal segments, enabling writes to arbitrary filesystem locations outside the intended root without error. This exposes operators syncing from untrusted buckets to potential unauthorized file writes. The patch changes the path resolution function to return an error and reject keys that escape the root directory.
Potential Impact
An attacker able to control or influence object keys in a source bucket can cause juicefs to write files outside the designated directory on the local filesystem. This can lead to unauthorized file writes at attacker-chosen locations, potentially overwriting critical files or planting malicious content. The vulnerability does not impact confidentiality or availability directly but has a high impact on integrity. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vendor has implemented a fix that changes the path resolution logic to reject keys that resolve outside the root directory. Until the fix is applied, operators should avoid syncing from buckets that are shared, public, or writable by untrusted parties to mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-21T10:30:49.467Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a883514acd9273b490dfd6c
Added to database: 08/21/2026, 11:23:00 UTC
Last enriched: 09/25/2026, 02:42:16 UTC
Last updated: 10/05/2026, 06:48:18 UTC
Views: 61
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.