Read the docs
TI-2026-74336 Aliases CVE-2026-100413

Hard-coded SSH host key in SeaweedFS SFTP Helm chart

Priority MEDIUM 64CWE-321Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Active
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-321.

Summary

SeaweedFS from 4.0.388 before 4.41 embeds an unencrypted Ed25519 SSH private host key in its SFTP Helm chart, a use of a hard-coded cryptographic key (CWE-321). A standalone SFTP deployment with the affected legacy settings presents that published host key, so an attacker who can redirect or intercept client traffic can impersonate the endpoint to clients that trust it and capture passwords or data sent to it. A public exploit is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00368 30th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed seaweedfs (seaweedfs): 4.41

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
seaweedfsseaweedfs4.0.388 to before 4.414.41Patch availableCNA
  • seaweedfs Vendorseaweedfs Affected 4.0.388 to before 4.41 Fixed in 4.41 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:seaweedfs:seaweedfs:*:*:*:*:*:*:*:*3.88 to before 4.41Vulnerableseaweedfs
  • cpe:2.3:a:seaweedfs:seaweedfs:*:*:*:*:*:*:*:* Versions 3.88 to before 4.41 Vulnerable ·seaweedfs

Remediation

Upgrade SeaweedFS to version 4.41, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA seaweedfs (seaweedfs) Fixed in 4.41

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-100413
  2. 2026-10-16 Priority changed: MEDIUM → LOW
  3. 2026-10-29 CISA SSVC decision points changed
  4. 2026-10-29 Priority changed: LOW → MEDIUM
  5. 2026-10-29 CVSS score added · NVD

References

Exploit 1

Patch 2

Other 1

  • TI-2026-39686 SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access CVSS 4.0HIGH 7.8
  • TI-2024-26879 seaweedfs v3.68 was discovered to contain a SQL injection vulnerability via the component… CVSS 3.1MEDIUM 6.5

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences