Skip to main content
VulnerabilityPublished Updated

CVE-2026-100413: seaweedfs · Use of Hard-coded Cryptographic Key

Affects seaweedfsSource CVE Database V5

0
Compare

Public exploit available · CVSS 7.0 High : upgrade to 4.41 as a priority.

Data as of 29 Oct 2026, 14:41 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.0
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-29.

Patch
Available – fixed in 4.41
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

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 14 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by GitHub, Inc.

    , 19 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 15 days after disclosure

  4. In Threat Radar

    record ingested

    , 15 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade seaweedfs and seaweedfs/seaweedfs to 4.41.

Affected software

ProductAffectedFixed in
seaweedfsseaweedfsAffected
  • >=4.0.388 <4.41
Fixed in
  • 4.41
GitHubseaweedfs/seaweedfspkg:github/seaweedfs/seaweedfsOther threatsAffected
  • >=4.0.388 <4.41
Fixed in
  • 4.41

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade SeaweedFS to version 4.41 or later, where this vulnerability is fixed. No other mitigation is required as the fix removes the hard-coded private key from the Helm chart and deployment templates.

Description

SeaweedFS versions from 4.0.388 up to but not including 4.41 contain a hard-coded unencrypted Ed25519 private host key in the SFTP Helm chart. This key could be exposed under certain deployment configurations, allowing an attacker who can intercept or redirect client traffic to impersonate the SFTP endpoint. This impersonation could lead to exposure of password credentials or data sent to the rogue endpoint. The vulnerability is fixed in version 4.41.

References

Community reviews

Loading reviews…