CVE-2026-100413: SeaweedFS · Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments
Affects seaweedfsSource GCVE Database
Not known to be exploited · CVSS 7.0 High : upgrade to 4.41.0 soon.
Data as of 30 Oct 2026, 12:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 7.0 |
|---|
- Patch
- Available – fixed in 4.41.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by GitHub, Inc.
, 19 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, 15 days after disclosure
In Threat Radar
record ingested
, 15 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade seaweedfs to 4.41.0.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamiseaweedfspkg:bitnami/seaweedfsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade SeaweedFS to version 4.41.0 or later, where this issue is fixed. Avoid using the legacy sftp.sshPrivateKey path and ensure that sftp.existingConfigSecret is supplied or that a hostKeysFolder provides a later Ed25519 signer to prevent the use of the hard-coded key. Since a patch is available and the issue is fixed in 4.41.0, applying this official fix is the recommended remediation.
Description
SeaweedFS versions from 4.0.388 up to but not including 4.41.0 contain a hard-coded unencrypted Ed25519 SSH private host key in the SFTP Helm chart. This key could be presented by certain standalone SFTP Helm deployments under specific configuration conditions, allowing an attacker who can intercept or redirect client traffic to impersonate the SFTP server. This impersonation could expose password credentials or data sent to the rogue endpoint. The issue is fixed in version 4.41.0.
References
- github.com/seaweedfs/seaweedfs/commit/742bd9f3aa9d9b83c9ad71389f66566f930acaa9 (opens in a new tab)
- github.com/seaweedfs/seaweedfs/pull/10390 (opens in a new tab)
- github.com/seaweedfs/seaweedfs/releases/tag/4.41 (opens in a new tab)
- github.com/seaweedfs/seaweedfs/security/advisories/GHSA-hqp5-j79g-vr89 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-100413 (opens in a new tab)