Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 3.1 7.7 HIGHEUVD CVSS 3.1 7.7 CVSS 3.1 · [email protected] · Secondary 7.7 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/seaweedfs/seaweedfs 0.0.0-20260612000715-b44cf51fe931osv · severity unknownFixed by github.com/seaweedfs/seaweedfs 0.0.0-20260612000715-b44cf51fe931KEV status unknown

cve-program · CVE-2026-55874

Published

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.

Read the publisher's advisory

euvd · EUVD-2026-42285

Published

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.

Read the publisher's advisory

nvd · CVE-2026-55874

Published

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.

Read the publisher's advisory

osv · GHSA-56wq-x3wv-3ff4

Published

### Summary The SeaweedFS S3 API gateway did not reject `..` path segments in the `X-Amz-Copy-Source` header used by `CopyObject` and `UploadPartCopy`. The request URL path was hardened against traversal in 4.30 (CVE-2026-54917), but the copy-source header was only checked for emptiness, so a `..` segment in the copy source survived into the server-side filer path and resolved into a different bucket. ### Impact A confused-deputy authorization bypass that breaks bucket isolation. IAM evaluates the caller's policy against the bucket named in the request URL (the destination the caller owns), while the copy reads its source from the traversed target bucket. An identity scoped to a single bucket (`Read` + `Write` on one bucket it controls) can therefore read any object in any bucket on the instance and land the result in its own bucket. For example, a caller authorized only for `bucket-a` issues a `CopyObject` into `bucket-a` with copy source `bucket-a/../<victim-bucket>/<key>`; the gateway reads `<victim-bucket>/<key>` and writes it to the attacker-controlled destination, from which the caller reads it normally. `UploadPartCopy` (CopyObjectPartHandler) is affected by the same vector. ### Affected versions All releases prior to 4.34. The 4.30 fix for CVE-2026-54917 hardened the request URL path but not the `X-Amz-Copy-Source` header. ### Patched version 4.34 and later. ### Remediation Upgrade to 4.34 or later. The fix validates the copy-source bucket and object key with the same `IsValidBucketName` / `IsValidObjectKey` guards already applied to the request URL, rejecting traversal segments before the handler runs, and applies the same check to `UploadPartCopy`. ### Workaround No configuration workaround. For deployments that cannot upgrade immediately, front the gateway with a reverse proxy that rejects requests whose `X-Amz-Copy-Source` header contains `..`, `%2e%2e`, or backslash sequences. ### References - Fix: https://github.com/seaweedfs/seaweedfs/pull/9929 (commit b44cf51fe931bd75aa4d37ae766bea90d7f85ccd) ### Credit Reported responsibly by [@47Cid](https://github.com/47Cid).

Read the publisher's advisory

osv · GO-2026-6327

Published

SeaweedFS: Path traversal in the S3 gateway X-Amz-Copy-Source header allows cross-bucket object read in github.com/seaweedfs/seaweedfs

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-55874

Published

seaweedfs

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "seaweedfs",
                    "product": "seaweedfs",
                    "versions": [
                        {
                            "version": "< 4.34",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-42285

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jul 8, 2026, 2:43:40 PM

dateUpdated: Jul 8, 2026, 5:01:02 PM

1 related source bulletins · separate from aliases

RHSA-2026:68333: Red Hat Security Advisory: Red Hat build of Cryostat security update

CVE-2026-15075 · CVE-2026-15076 · CVE-2026-16308 · CVE-2026-33818 · CVE-2026-41178 · CVE-2026-45112 · CVE-2026-48586 · CVE-2026-49978 · CVE-2026-54399 · CVE-2026-54428 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-55851 · CVE-2026-55874 · CVE-2026-55969 · CVE-2026-56745 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-56854 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-58372 · CVE-2026-59869 · CVE-2026-59877 · CVE-2026-59899 · CVE-2026-68494 · CVE-2026-69152 · CVE-2026-69192

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-55874

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-22

Original publisher date fields

published: 2026-07-08T15:16:30.320

lastModified: 2026-07-08T18:16:33.270

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-56wq-x3wv-3ff4

Published

github.com/seaweedfs/seaweedfs

Go

SEMVER · introduced 0 → fixed 0.0.0-20260612000715-b44cf51fe931

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2026-6327

Published

github.com/seaweedfs/seaweedfs

Go

SEMVER · introduced 0 → fixed 0.0.0-20260612000715-b44cf51fe931

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 18:50 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current