juicedata juicefs up to 1.3.1 /debug/pprof/cmdline debug code
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 1.42+ |
Summary
A vulnerability, which was classified as problematic, was found in juicedata juicefs up to 1.3.1. The affected element is an unknown function of the file /debug/pprof/cmdline. Such manipulation leads to debug code. This vulnerability is documented as CVE-2026-59092. The attack needs to be performed locally. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in juicedata juicefs up to 1.3.1. Affected by this issue is some unknown functionality of the file /debug/pprof/cmdline. The manipulation with an unknown input leads to a debug code vulnerability. Using CWE to declare the problem leads to CWE-489. The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information. Impacted is confidentiality, integrity, and availability. CVE summarizes:
JuiceFS through 1.3.1, fixed in commit a46979c, contains an authentication bypass vulnerability that allows unauthenticated remote attackers to access sensitive debug and metrics endpoints by exploiting improper handler registration on the shared http.DefaultServeMux. Attackers can request the /debug/pprof/cmdline endpoint to obtain the process command line containing metadata engine connection strings with database credentials, granting full read/write access to filesystem metadata, while other pprof handlers leak internal state and profiling handlers enable denial of service.
The weakness was released by George Chen as 7213. The advisory is available at github.com. This vulnerability is handled as CVE-2026-59092 since 07/02/2026. The exploitation is known to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit.
Upgrading eliminates this vulnerability. Applying the patch a46979cdd4082217081ee99b931ddc53d038e47a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.7
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Debug codeCWE: CWE-489
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Patch: a46979cdd4082217081ee99b931ddc53d038e47a
Timeline
07/02/2026 Advisory disclosed07/02/2026 CVE reserved
07/02/2026 VulDB entry created
07/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 7213
Researcher: George Chen
Status: Confirmed
CVE: CVE-2026-59092 (🔒)
GCVE (CVE): GCVE-0-2026-59092
GCVE (VulDB): GCVE-100-375986
Entry
Created: 07/02/2026 22:35Changes: 07/02/2026 22:35 (78)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.