Tools / sftpgo / Security

Security Deep Dive

sftpgo

Security posture and CVE patch evidence from tracked releases.

Back to Tool

1 critical dependency CVE affects v2.7.3.

Audit transitive dependencies; consider upgrading or pinning replacements.

Versions by Severity

CVEs are attributed to tracked releases published before the patch release.

2 versions tracked

Version	Published	C	H	M	L	KEV	Notes
v2.7.3	2026-05-30	—	—	—	—	—	Latest
v2.7.1	2026-03-13	—	—	—	—	—	Patches GHSA-x8qh-7475-c5mp Patches GO-2026-4697 Patches GO-2026-4699

— Signed — SLSA — SBOM ✓ Security policy Unknown cadence 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 Present

GitHub repository metadata Repository policy

Checked: 18d ago

Release cadence Unknown

12-release median Release history

Latest release: 4d ago

Maintainer active Present

Recent commit activity Repository

Last commit: 3d ago

Checksums (SHA256SUMS) Not active yet

SHA256SUMS or equivalent Release asset

Latest release: 4d ago

GitHub Actions attestation Not active yet

actions/attest-build-provenance Workflow file

Latest release: 4d ago

Signing assets Not active yet

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

Latest release: 4d ago

3.9/10 Security Score

5.1/10 Scorecard

0d avg CVE Patch Speed

Open CVEs Open CVEs detected for latest version.

Patch speed: 0d

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

3d stale

scorecard

2.04 / 4.0

Score 5.1/10

cve health

0.00 / 2.5

Open CVEs detected

patch speed

0.50 / 0.5

0d avg

kev exposure

1.50 / 1.5

No KEV exposure

supply chain risk

-1.40 / 10.0

Risk 14.0/100

Score breakdown

schema v2

Vulnerability posture

vulnerability posture

0.0

25%

direct cves: open cve scan: available

Release responsiveness

release responsiveness

10.0

patch speed days: 0

Dependency exposure

dependency exposure

8.6

10%

supply chain risk: 14.0 transitive cves: 1c/5h

Provenance trust

provenance trust

5.1

40%

scorecard score: 5.1 openssf badge: none

Maintainer health

maintainer health

10.0

10%

activity freshness: 3d

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 14.0/100

1 Transitive critical CVEs

0 KEV-transitive CVEs

100% Dependency freshness

Scorecard

Scorecard 5.1/10

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

Check	Score	Reason
Code-Review	0	Found 0/29 approved changesets -- score normalized to 0
Maintained	10	30 commit(s) and 9 issue activity found in the last 90 days -- score normalized to 10
Security-Policy	10	security policy file detected
Dangerous-Workflow	10	no dangerous workflow patterns detected
Binary-Artifacts	10	no binaries found in the repo
Token-Permissions	0	detected GitHub workflow tokens with excessive permissions
CII-Best-Practices	2	badge detected: InProgress
Fuzzing	0	project is not fuzzed
License	10	license file detected
Branch-Protection	0	branch protection not enabled on development/release branches
Signed-Releases	0	Project has not signed or included provenance with any releases.
Pinned-Dependencies	0	dependency not pinned by hash detected -- score normalized to 0
SAST	10	SAST tool is run on all commits
Packaging	10	packaging workflow detected

CVE Patch History

Median patch time: 0 days

Tracks CVEs that were addressed in tagged releases. Shorter gap between disclosure and patch = faster response. EPSS = predicted probability of exploitation in next 30 days (FIRST.org); colored at ≥90%ile and ≥50%ile.

CVEs Patched by Year

Critical High Medium Low

2026

CVE	Severity	EPSS	Disclosed	Fixed in	Days to fix	vs Ecosystem Median	KEV
GHSA-x8qh-7475-c5mp	unknown	—	—	v2.7.1	—	—	—
GO-2026-4697	unknown	—	—	v2.7.1	—	—	—
GO-2026-4699	unknown	—	—	v2.7.1	—	—	—

KEV = CISA Known Exploited Vulnerabilities catalog — actively exploited in the wild.

Dependency Vulnerabilities

266 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 (13) All (13)

Critical 1 High 5 Medium 4 Unknown 3

CVE	Severity	KEV	Dependency	Affected version	Cleared in release
CVE-2024-45337	critical	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2021-38561	high	—	golang.org/x/text	0.3.5	v2.7.3
CVE-2021-43565	high	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2022-27191	high	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2022-32149	high	—	golang.org/x/text	0.3.5	v2.7.3
CVE-2025-22869	high	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2022-29526	medium	—	golang.org/x/sys	0.0.0-20210124154548-22da62e12c0c	v2.7.3
CVE-2023-48795	medium	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2025-47914	medium	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2025-58181	medium	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2022-30636	unknown	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2025-47913	unknown	—	golang.org/x/crypto	0.0.0-20201221181555-eec23a3978ad	v2.7.3
CVE-2025-69725	unknown	—	github.com/go-chi/chi	1.5.2	v2.7.3

Showing 13 of 13