CVE-2026-77763

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-21. the CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, ghsa
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

August 21, 2026

Last Modified

August 21, 2026

Advisory Details (6)

Auto-updated Aug 21, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

JuiceFS Local Filestore Backend Joins Object Keys onto the Storage Root Without a Containment Check, Allowing Writes Outside the Configured Directory | Advisories | VulnCheck

https://www.vulncheck.com/advisories/juicefs-local-filestore-backend-joins-object-keys-onto-the-storage-root-without-a-containment-check-allowing-writes-outside-the-configured-directory
github_pr

object/file: reject object keys that escape the filestore root

Fix merged in juicedata/juicefs PR #7425 on 2026-08-21 — awaiting tagged release

https://github.com/juicedata/juicefs/pull/7425
generic

Local filestore object backend writes outside its configured root via a crafted object key · Issue #7401 · juicedata/juicefs · GitHub

https://github.com/juicedata/juicefs/issues/7401
github_commit

commit 0bcd70b3d130 (juicedata/juicefs)

Fix landed in juicedata/juicefs commit 0bcd70b3d130 — awaiting tagged release

https://github.com/juicedata/juicefs/commit/0bcd70b3d13088d38127d6fb5750c91be7c4ec16
generic

juicefs/pkg/object/file.go at v1.4.1 · juicedata/juicefs · GitHub

https://github.com/juicedata/juicefs/blob/v1.4.1/pkg/object/file.go
generic

GitHub - juicedata/juicefs: JuiceFS is a distributed POSIX file system built on top of Redis and S3. · GitHub

https://github.com/juicedata/juicefs

Vendor Advisories for CVE-2026-77763(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 21:52 UTCEG score recompute
  2. 2026-08-21 21:52 UTCGHSA enrichment
  3. 2026-08-21 11:21 UTCEG score recompute
  4. 2026-08-21 11:16 UTCEG score recompute
  5. 2026-08-21 11:14 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-77763?
CVE-2026-77763 is a medium vulnerability published on August 21, 2026. 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.…
When was CVE-2026-77763 disclosed?
CVE-2026-77763 was first published in the National Vulnerability Database on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-77763?
CVE-2026-77763 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-77763?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-77763, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-77763

Explore →

Is Your Infrastructure Affected by CVE-2026-77763?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.