Tools / JuiceFS / Security

Security Deep Dive

JuiceFS

Security posture and CVE patch evidence from tracked releases.

Back to Tool

12 high-severity dependency CVEs affects v1.4.0-beta2.

Review the dependency vulnerabilities below.

— Signed — SLSA — SBOM ✗ Security policy Monthly cadence · 29d median Active maintainer

Trust Signals — 2 of 9 Present

Evidence already collected from releases and repository metadata.

2/9 Present

Signed releases Unknown

Latest release artifact signature Latest release

—

SLSA provenance Unknown

Attestation predicate level Latest release

—

SBOM published Unknown

GitHub SBOM API Latest release

—

SECURITY.md Absent

GitHub repository metadata Repository policy

Checked: 23d ago

Release cadence: monthly Present

29d median over recent releases Release history

Latest release: 5d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 1d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 5d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 5d ago

Signing assets Not active yet

.sig, .crt, cosign.pub, or similar Release asset

Latest release: 5d ago

3.5/10 Security Score

4.3/10 Scorecard

Dependency Exposure 24 transitive dependency CVEs found in the latest SBOM.

Security Score

A composite score aggregating Scorecard performance, CVE patch history, OpenSSF badge tier, and dependency vulnerability exposure. Score ≥ 7.0 is healthy; < 4.0 warrants attention.

epss

0.25 / 0.5

No EPSS data

freshness

1.00 / 1.0

1d stale

scorecard

1.72 / 4.0

Score 4.3/10

cve health

0.00 / 2.5

No open CVEs

patch speed

0.50 / 0.5

⚠ Estimated — no CVE patch history

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.50 / 10.0

Risk 66.6/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: clear cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: no_history

Dependency exposure

dependency exposure

3.3

10%

supply chain risk: 66.58 transitive cves: 3c/27h

Provenance trust

provenance trust

4.3

40%

scorecard score: 4.3 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 1d

Operational risk

operational risk

8.5

10%

kev exposure: clear epss max: none

How is this calculated?

The six dimensions group the legacy score signals into weighted categories: direct vulnerability status, patch responsiveness, dependency exposure, provenance checks, maintainer activity, and exploitability risk. The flat component values above remain available for compatibility.

Supply Chain Risk

Risk 66.6/100

0 Transitive critical CVEs

0 KEV-transitive CVEs

71% Dependency freshness

Scorecard

Scorecard 4.3/10

OpenSSF Scorecard evaluates supply-chain security practices automatically. Score ≥ 6 is passing; ≥ 8 is excellent.

Check	Score	Reason
Code-Review	10	all changesets reviewed
Maintained	10	30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices	0	no effort to earn an OpenSSF best practices badge detected
Security-Policy	0	security policy file not detected
Binary-Artifacts	10	no binaries found in the repo
Dangerous-Workflow	0	dangerous workflow patterns detected
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
Fuzzing	0	project is not fuzzed
License	10	license file detected
Branch-Protection	-1	internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
Signed-Releases	0	Project has not signed or included provenance with any releases.
Packaging	10	packaging workflow detected
SAST	7	SAST tool detected but not run on all commits
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0

Dependency Vulnerabilities

984 dependencies scanned View full dependency list →

Scanning the SBOM (Software Bill of Materials) of the latest release for known vulnerabilities in transitive dependencies.

Critical

High

Medium

Low

Unknown

Still affecting latest (24) All (62)

High 12 Medium 9 Low 1 Unknown 2

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2023-28452	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2025-47950	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2025-58063	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-26017	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-26018	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-32934	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-32936	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-33190	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-33489	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-35579	high	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-42151	high	—	github.com/prometheus/prometheus	v0.54.1	v1.4.0-beta2
CVE-2026-42154	high	—	github.com/prometheus/prometheus	v0.54.1	v1.4.0-beta2
CVE-2022-2835	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2022-2837	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2023-30464	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2024-0874	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2025-68151	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-33750	medium	—	brace-expansion	1.1.12	v1.4.0-beta2
CVE-2026-40179	medium	—	github.com/prometheus/prometheus	v0.54.1	v1.4.0-beta2
GHSA-fw8g-cg8f-9j28	medium	—	github.com/prometheus/prometheus	v0.54.1	v1.4.0-beta2
GHSA-gv9j-4w24-q7vx	medium	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2
CVE-2026-26958	low	—	filippo.io/edwards25519	v1.1.0	v1.4.0-beta2
CVE-2026-33814	unknown	—	golang.org/x/net	v0.52.0	v1.4.0-beta2
GO-2022-0368	unknown	—	github.com/coredns/coredns	v1.4.0	v1.4.0-beta2

Showing 24 of 62