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

> Attackers can impersonate SFTP endpoints using a hardcoded SSH key in specific Helm deployments, exposing credentials and data to interception.

- **Severity:** High 7.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** BIT-seaweedfs-2026-100413, GHSA-hqp5-j79g-vr89

## What is CVE-2026-100413?

CVE-2026-100413 is a high-severity vulnerability in seaweedfs, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-100413?

1 open source package ship an affected version, including seaweedfs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `seaweedfs` | Bitnami | From 4.0.388 | 4.41.0 |

Products: Seaweedfs Seaweedfs.

## How do I fix CVE-2026-100413?

Upgrade seaweedfs to 4.41.0 or later.

## Is CVE-2026-100413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100413 exists.

## Other vulnerabilities in seaweedfs

- [CVE-2026-54917](https://insights.sbomify.com/CVE-2026-54917/): SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access (high 7.8)
- [CVE-2024-40120](https://insights.sbomify.com/CVE-2024-40120/): SeaweedFS Vulnerable to SQL Injection (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100413 and fix it if it is affected.

What it is: CVE-2026-100413 is a high-severity vulnerability in seaweedfs, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100413 exists.

Affected packages and fixed versions:
- seaweedfs (Bitnami): affected from 4.0.388; fixed in 4.41.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100413/ (Markdown: https://insights.sbomify.com/CVE-2026-100413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100413
- OSV: https://osv.dev/vulnerability/CVE-2026-100413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100413/
Summaries are generated and may contain mistakes; the official description above is the record.