SeaweedFS Helm chart: embedded SFTP host key lets anyone impersonate the storage endpoint

Impact

From 4.0.388 until 4.41 the SeaweedFS SFTP Helm chart shipped one unencrypted Ed25519 private host key in sftp-secret.yaml, so every standalone deployment that took the legacy sftp.sshPrivateKey path presented the same publicly known host identity. An attacker able to intercept or redirect client traffic can stand up a rogue SFTP endpoint that clients accept, harvesting passwords and the data being uploaded. On a GPU fleet this is the object/file store that training jobs and dataset staging pull from, so the credentials and payloads at risk are the ones that feed the cluster. The record notes the key only loads when sftp.enabled and sftp.enableAuth are set, no sftp.existingConfigSecret is supplied, and hostKeysFolder provides no later Ed25519 signer; default all-in-one and non-authenticated standalone paths did not load it.

Who can reach it

Anyone positioned to intercept or redirect SFTP client traffic on the network path to the SeaweedFS SFTP endpoint. No authentication needed; clients must have trusted the published host key, and the deployment must match the configuration above.

What to do

Upgrade to SeaweedFS 4.41 and - because the old key is public - generate a fresh host key, supply it through sftp.existingConfigSecret or hostKeysFolder, and redistribute the new host fingerprint to clients. Rotate any password credentials that clients may have sent to the affected endpoint. Restarting the SFTP pods is enough; no node work.

References

Related entries

• Sidero Omni: SAML assertion replay race lets a captured saml-session token be redeemed more than onceCVE-2026-45720 · Sidero Omni (SAML session interceptor, internal/pkg/auth/interceptor/saml.go)High
• Redis (multi-bulk command protocol handling): PERMANENT, VENDOR-ACKNOWLEDGED DENIAL OF SERVICE WITH NO FIX PLANNED. AnNCVD-2025-021-redis-multi-bulk-command-protoco · Redis (multi-bulk command protocol handling)High
• AMD AGESA bootloader - DDR5 PMIC default configuration: The AGESA bootloader leaves DDR5 memory modules in an insecureCVE-2025-48516 · AMD AGESA bootloader - DDR5 PMIC default configurationMedium
• AMD Graphics Driver - out-of-bounds write: Improper input validation lets a local attacker write out of bounds throughCVE-2025-48518 · AMD Graphics Driver - out-of-bounds writeMedium
• go-witness: AWS attestor accepts unsigned or forged EC2 instance identity documentsCVE-2025-62375 · in-toto go-witness / witness (AWS EC2 instance identity document attestor)Medium
• OneUptime: password reset tokens written to INFO logs allow account takeover from log accessCVE-2026-32598 · OneUptime (password reset flow, INFO-level logging of reset URL)Medium