CVE-2026-100413

SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments

State
Published
Severity
7.0 High
Published
Oct 14, 2026
Updated
Oct 29, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

SeaweedFS is a distributed storage system for files and blobs. From 4.0.388 until 4.41, the SFTP Helm chart embedded one unencrypted Ed25519 private host key in k8s/charts/seaweedfs/templates/sftp/sftp-secret.yaml as stringData.seaweedfs_sftp_ssh_private_key. A standalone deployment presented that public key when sftp.enabled and sftp.enableAuth were true, sftp.existingConfigSecret was not supplied, the legacy sftp.sshPrivateKey path remained selected, a valid config-ssh Secret allowed startup, and hostKeysFolder did not provide a later Ed25519 signer. An attacker able to redirect or intercept client traffic could impersonate that SFTP endpoint to clients that trusted the published host identity, exposing password credentials or data sent to the rogue endpoint. Default all-in-one and non-authenticated standalone paths did not load the key. This issue is fixed in version 4.41.

Scores

CVSSScoreVectorSource
4.07.0 HighCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:NGitHub_M

Weaknesses

  • CWE-321 Use of Hard-coded Cryptographic Key

Affected Products

ProductVersions
seaweedfsseaweedfs
  • >= 4.0.388, < 4.41Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.