PoC Monitor
← All CVEs
CVE-2026-100413published 14 Oct 2026 18:03 UTCData: JSON · API

SeaweedFS

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.1high · scored by NVD · CWE-321
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

seaweedfs seaweedfs
  • >= 4.0.388, < 4.41

Fixed in 4.41

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published14 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.