Skip to content
Fencer Vulns
high 7.7

CVE-2026-55874 json

SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read

published 2026-07-08 4 mo ago modified 2026-09-02 2 mo ago also BIT-seaweedfs-2026-55874 , EUVD-2026-42285 , GHSA-56wq-x3wv-3ff4 , GO-2026-6327

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 49%
public exploits
0
none known

Summary

SeaweedFS is a distributed storage system. Prior to 4.34, the S3 API gateway does not reject dot-dot path segments in the X-Amz-Copy-Source header used by CopyObject and UploadPartCopy, allowing an authenticated identity scoped to one bucket to read objects from other buckets through server-side copy. This issue is fixed in version 4.34.

Patch / fix

  • go github.com/seaweedfs/seaweedfs 0.0.0-20260612000715-b44cf51fe931
  • bitnami seaweedfs 4.34.0
  • seaweedfs seaweedfs 4.34
  • govulncheck-vulndb SLES 16.0, SLES for SAP applications 16.0 0.0.20260902T191204-160000.1.1

suse advisories SUSE-SU-2026:23692-1SUSE-SU-2026:23712-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260902T191204-160000.1.1

opensuse advisories openSUSE-SU-2026:21812-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-55874 updated cvss 7.7

SeaweedFS: github.com/seaweedfs/seaweedfs: SeaweedFS: Information disclosure via S3 API gateway path traversal

  • Red Hat Cryostat 4 on RHEL 9 cryostat/cryostat-storage-rhel9 4.2.0-22
    fixed: vendor fix RHSA-2026:68333
  • Red Hat Cryostat 4 on RHEL 9 cryostat/cryostat-rhel9 4.2.0-14, cryostat/cryostat-db-rhel9 4.2.0-22, cryostat/jfr-datasource-rhel9 4.2.0-14, cryostat/cryostat-reports-rhel9 4.2.0-14, cryostat/cryostat-rhel9-operator 4.2.0-21, cryostat/cryostat-operator-bundle 4.2.0-12, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
OSV 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/seaweedfs/seaweedfs
<0.0.0-20260612000715-b44cf51fe931
0.0.0-20260612000715-b44cf51fe931
bitnami seaweedfs
<4.34.0
4.34.0

Affected products

  • seaweedfs seaweedfs

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.