CVE-2026-100413
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 36% of all known CVEs.
References
Related Vulnerabilities
Other CWE-321 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-30406 | Critical | 9.0 | 94% | KEV | Fix |
| CVE-2016-4437 | Critical | 9.8 | 93% | KEV | Fix |
| CVE-2023-32169 | Critical | 9.8 | 56% | - | - |
| CVE-2023-27584 | Critical | 9.8 | 34% | - | Fix |
| CVE-2020-10884 | High | 8.8 | 22% | - | - |
| CVE-2021-4228 | Medium | 5.8 | 9.9% | - | - |
Common questions
How do I fix CVE-2026-100413?
No published fix for CVE-2026-100413 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-100413 being actively exploited?
Not that we know of. CVE-2026-100413 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.42% is the estimated probability that it will be exploited in the next 30 days. That is higher than 36% of all scored CVEs.
How severe is CVE-2026-100413?
CVE-2026-100413 has a CVSS v4 base score of 7.0, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-100413
Markdown
[](https://tridentstack.com/cve/CVE-2026-100413)HTML
<a href="https://tridentstack.com/cve/CVE-2026-100413"><img src="https://tridentstack.com/cve/badge/CVE-2026-100413.svg" alt="CVE-2026-100413"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-16.