CVE-2026-100413

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-14 18:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-29 18:43 UTC Last updatedMost recent change to the record

Details

Published

2026-10-14 18:17 UTC

Last modified

2026-10-29 18:43 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-321

Record status

Analyzed

Affected

• Seaweedfs < 4.41

Attack profile CVSS 4.0 · 7.0

Attack vector

Network

Complexity

High

Attack requirements

Present

Privileges needed

None

User interaction

Active

Confidentiality

High

Integrity

Low

Availability

None