CVE-2026-100413 seaweedfs CVE debrief

Who should care

Defenders responsible for SeaweedFS SFTP deployments should assess exposure and prioritize verification and remediation to mitigate potential impersonation risks. This includes verifying SFTP configurations, upgrading to version 4.41 or later, and reviewing and updating SFTP Helm chart configurations to avoid presenting the hard-coded public key. Additionally, defenders should review compensating controls for exposed systems, check relevant monitoring and

Why it matters

The hard-coded SSH host key issue in SeaweedFS SFTP Helm deployments requires verification and remediation to mitigate potential impersonation risks.

• An attacker could impersonate the SFTP endpoint to clients that trust the published host identity, potentially exposing password credentials or data sent to the rogue endpoint.
• Defenders should verify SFTP configurations to ensure the hard-coded public key is not presented.
• Remediation priority is high for deployments using affected versions and configurations.

Technical summary

The SeaweedFS SFTP Helm chart embedded a hard-coded Ed25519 private host key from version 4.0.388 until 4.41. Certain standalone deployments presented this public key, allowing potential impersonation of the SFTP endpoint. The issue is fixed in version 4.41. Defenders should prioritize verifying SFTP configurations and upgrading to version 4.41 to mitigate potential impersonation risks. The fix involves updating the SFTP Helm chart to use a secure method for generating and managing host keys, rather than relying on a hard-coded key.

Defensive priority

Defenders should prioritize verifying SFTP configurations and upgrading to version 4.41 to mitigate potential impersonation risks.

Recommended defensive actions

• Verify SFTP configurations to ensure sftp.existingConfigSecret is supplied and hostKeysFolder provides a valid Ed25519 signer.
• Upgrade to SeaweedFS version 4.41 or later to fix the hard-coded SSH host key issue.
• Review and update SFTP Helm chart configurations to avoid presenting the hard-coded public key.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source item provide details on the hard-coded SSH host key issue in SeaweedFS SFTP Helm deployments. The issue is fixed in version 4.41. The CVE record was published on 2026-10-14T18:03:12.709Z and has not been modified since then. There are no additional details on the number of affected deployments or specific exploitation attempts. Defenders should verify SFTP configurations to ensure the hard-coded public key is not presented and prioritize remediation for deployments using affected versions and configurations.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.