{"answers":{"affected":"1 open source package ship an affected version, including seaweedfs. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100413 exists.","fix":"Upgrade seaweedfs to 4.41.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-100413 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100413 exists.\n\nAffected packages and fixed versions:\n- seaweedfs (Bitnami): affected from 4.0.388; fixed in 4.41.0\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100413/ (Markdown: https://insights.sbomify.com/CVE-2026-100413/index.md)","id":"CVE-2026-100413","markdown":"https://insights.sbomify.com/CVE-2026-100413/index.md","name":"CVE-2026-100413","record":{"aliases":["BIT-seaweedfs-2026-100413","GHSA-hqp5-j79g-vr89"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"SeaweedFS Helm chart","requires_auth":"none","summary":"Attackers can impersonate SFTP endpoints using a hardcoded SSH key in specific Helm deployments, exposing credentials and data to interception.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"seaweedfs","vendor":"seaweedfs"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"SeaweedFS: Hard-coded SSH host key can be presented by certain standalone SFTP Helm deployments","id":"CVE-2026-100413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"RustDesk before 1.5.0 One-Way File Transfer Bypass","id":"CVE-2026-100417"},"packages":[{"ecosystem":"Bitnami","fixed":["4.41.0"],"introduced":["4.0.388"],"last_affected":[],"package":"seaweedfs","purl":"pkg:bitnami/seaweedfs","source":"BIT-seaweedfs-2026-100413"}],"prev":{"headline":"OpenNext Cloudflare: Cache interception can bypass middleware protection for encoded paths","id":"CVE-2026-100409"},"products":["seaweedfs"],"published":"2026-10-14","related":[{"cvss_score":7.8,"headline":"SeaweedFS: Path traversal in the S3 and Iceberg REST gateways allows cross-bucket access","id":"CVE-2026-54917","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.5,"headline":"SeaweedFS Vulnerable to SQL Injection","id":"CVE-2024-40120","kev_date_added":null,"published":"2025-05-16"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["seaweedfs"]},"summary":"Attackers can impersonate SFTP endpoints using a hardcoded SSH key in specific Helm deployments, exposing credentials and data to interception.","url":"https://insights.sbomify.com/CVE-2026-100413/"}