CVE-2026-59092: JuiceFS through 1.3.1, fixed in commit a46979c, contains an authentication bypass vulnerability that allows un

Q: How do I fix CVE-2026-59092?

juicefs: upgrade to newer than 1.3.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-59092 being exploited?

CVE-2026-59092 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-59092 affect?

CVE-2026-59092 affects juicefs. Severity is high (CVSS 7.7). 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

This month

HIGH 7.7UPGRADE

CVE-2026-59092 is a high-severity flaw (CVSS 7.7) affecting juicefs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 rea

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 49%)
CISA exploited list	No
Weakness	CWE-489
Published	2026-07-02
Last modified	2026-10-25

Publisher (CNA): VulnCheck · Vendor: juicedata

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-02 20:17 UTCPublished CVE record published
2026-10-25 21:10 UTCUpdated Record last modified

juicedata juicefs UPGRADE

Affected: <= 1.3.1

Fixed in: newer than 1.3.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy juicefs || rpm -q juicefs || juicefs --version

2. UPGRADE to newer than 1.3.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade juicefs

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade juicefs

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59092?

juicefs: upgrade to newer than 1.3.1. Exact commands for each OS are on this page.

Is CVE-2026-59092 being exploited?

CVE-2026-59092 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59092 affect?

CVE-2026-59092 affects juicefs. Severity is high (CVSS 7.7). 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

How urgent is CVE-2026-59092?

Priority 40/100. High severity

References

← Back to latest CVEs