Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.
CVE-2026-100413
SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments
AV AC AT PR UI VC VI VA CVSS EPSS %ile KEV
N H P N A H L N 7.0 .0037 31.3 —
AFFECTED
Product Versions Fixed
seaweedfs >= 4.0.388, < 4.41 – —
TIMELINE
Sep 25 Reserved by GitHub_M
Oct 14 Published (CNA: GitHub_M)
Oct 29 EXPLOIT PUBLISHED — CVE-2026-100413 (seaweedfs). Public exploit reference added.
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.
Lifecycle
Complete event history — 3 events, chronological
| Date | Event | Detail |
| September 25, 2026 | Reserved | Reserved by GitHub_M |
| October 14, 2026 | Published | Published (CNA: GitHub_M) |
| October 29, 2026 | EXPLOIT PUBLISHED | EXPLOIT PUBLISHED — CVE-2026-100413 (seaweedfs). Public exploit reference added. |
Affected
Affected products and packages — 1 row
| Vendor | Product / Package | Ecosystem | Version introduced | Fixed |
| seaweedfs | seaweedfs | — | >= 4.0.388, < 4.41 | — |
About this page
This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-100413 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.