CVE-2026-77375 json
SFTPGo: Denial of service via malformed SSH channel request
published 2026-10-13 26 d ago modified 2026-10-19 20 d ago also GHSA-q7pc-356p-hggc , GO-2026-6792 , EUVD-2026-98780
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
SFTPGo is an open source, event-driven file transfer solution. Prior to 2.7.5, an authenticated SSH user can send a malformed protocol message while opening a channel, causing an unhandled error that terminates the server process and affects all connected users until restart. No confidentiality or integrity impact has been identified. This issue is fixed in 2.7.5.
Patch / fix
- go github.com/drakkan/sftpgo/v2 2.7.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 26 d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/drakkan/sftpgo/v2 | <2.7.5 |
2.7.5 |
| go | github.com/drakkan/sftpgo | all versions |
no fix listed |
Affected products
- drakkan sftpgo
Classification
- Weakness
-
- CWE-129 Improper Validation of Array Index
References
-
github.com
/drakkan/sftpgo/commit/4f751232d7025cf2f7360e01ee8dca81e74b48b0
web, patch
-
github.com
/drakkan/sftpgo/security/advisories/GHSA-q7pc-356p-hggc
web, advisory
-
github.com
/drakkan/sftpgo/releases/tag/v2.7.5
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-77375
advisory
-
github.com
/drakkan/sftpgo
package
Sources
- CVE List CVE-2026-77375
- GitHub Advisory GHSA-q7pc-356p-hggc
- NVD CVE-2026-77375
- OSV GO-2026-6792
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.