Every CVE Search/ Get API key

CVE-2026-55874

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

7.7 HighFix available

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.

Attack profile

How easy it is to exploit

Attack vector
Network
Complexity
Low
Privileges needed
Low
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

0.61%Up 0.3 points since Jul 9, 2026
90%50%10%1%

What each source reports

CVE List Score used 7.7

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

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.

Record
CVE-2026-55874
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-22
Updated
2026-11-02
EUVDEUVD-2026-42285 7.7

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.

Record
EUVD-2026-42285
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Updated
2026-11-02
GitHub AdvisoriesGHSA-56wq-x3wv-3ff4 7.7

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

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

Credit

Reported responsibly by @47Cid.

Record
GHSA-56wq-x3wv-3ff4
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-22
Updated
2026-11-02
NVD 7.7

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.

Record
CVE-2026-55874
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-22
Updated
2026-11-02
OSV 7.7

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

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.

Record
CVE-2026-55874
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-22
Updated
2026-11-02
OSVGHSA-56wq-x3wv-3ff4 7.7

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

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

Credit

Reported responsibly by @47Cid.

Record
GHSA-56wq-x3wv-3ff4
CVSS 3.1
7.7 HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weakness
CWE-22
Updated
2026-11-02
Show 5 moreShow less
OSVBIT-seaweedfs-2026-55874 No score

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

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.

Record
BIT-seaweedfs-2026-55874
Updated
2026-11-02
OSVGO-2026-6327 No score

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

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

Record
GO-2026-6327
Updated
2026-11-02
OSVopenSUSE-SU-2026:21812-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
  • GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
  • GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
  • GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
  • GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
  • GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
  • GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
  • GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
  • GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
  • GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
  • GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
  • GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
  • GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
  • GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
  • GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
  • GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
  • GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
  • GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
  • GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
  • GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
  • GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
  • GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
  • GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
  • GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
  • GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
  • GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
  • GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
  • GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
  • GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
  • GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
  • GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
  • GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
  • GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
  • GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
  • GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
  • GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
  • GO-2026-6354 CVE-2026-78662
  • GO-2026-6355 CVE-2026-56855
  • Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
  • GO-2026-6303 CVE-2026-56854
Record
openSUSE-SU-2026:21812-1
Updated
2026-11-02
OSVSUSE-SU-2026:23692-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
  • GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
  • GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
  • GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
  • GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
  • GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
  • GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
  • GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
  • GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
  • GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
  • GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
  • GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
  • GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
  • GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
  • GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
  • GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
  • GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
  • GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
  • GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
  • GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
  • GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
  • GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
  • GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
  • GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
  • GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
  • GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
  • GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
  • GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
  • GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
  • GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
  • GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
  • GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
  • GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
  • GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
  • GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
  • GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
  • GO-2026-6354 CVE-2026-78662
  • GO-2026-6355 CVE-2026-56855
  • Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
  • GO-2026-6303 CVE-2026-56854
Record
SUSE-SU-2026:23692-1
Updated
2026-11-02
OSVSUSE-SU-2026:23712-1 No score

Security update for govulncheck-vulndb

This update for govulncheck-vulndb fixes the following issues:

  • Update to version 0.0.20260902T191204 2026-09-02T19:12:04Z (jsc#PED-11136).

Go CVE Numbering Authority IDs added or updated with aliases:

  • GO-2026-6305 CVE-2026-55834 GHSA-2wvm-8mvp-22qv
  • GO-2026-6306 CVE-2026-55064 GHSA-44v6-7fxq-vgf4
  • GO-2026-6307 CVE-2026-55067 GHSA-569v-q83c-3j3g
  • GO-2026-6308 CVE-2026-55066 GHSA-5pg6-m483-7vrg
  • GO-2026-6309 CVE-2026-54746 GHSA-8x7x-83cf-c3pg
  • GO-2026-6310 CVE-2026-54755 GHSA-cgc5-v3f2-8m2v
  • GO-2026-6311 CVE-2026-54766 GHSA-f27p-pw2p-9pr4
  • GO-2026-6312 CVE-2026-55108 GHSA-fmgp-q6jx-gg3x
  • GO-2026-6313 CVE-2026-55065 GHSA-gg93-x632-9ccv
  • GO-2026-6314 CVE-2026-55569 GHSA-mf5c-hw34-4hpp
  • GO-2026-6315 CVE-2026-54754 GHSA-p7gw-2pcp-5pf8
  • GO-2026-6316 CVE-2026-55068 GHSA-x8mj-6p3q-g5pp
  • GO-2026-6317 CVE-2026-55588 GHSA-298f-872v-2rcx
  • GO-2026-6318 CVE-2026-55621 GHSA-64f3-v33m-w89f
  • GO-2026-6319 CVE-2026-55622 GHSA-c9f5-j9c3-mhrg
  • GO-2026-6320 CVE-2026-55245 GHSA-w98g-5w9p-p3rc
  • GO-2026-6321 CVE-2026-55484 GHSA-hr6j-w4mw-g9mj
  • GO-2026-6322 CVE-2026-55678 GHSA-p378-jp5r-gpgw
  • GO-2026-6323 CVE-2026-55763 GHSA-v358-wf77-39xv
  • GO-2026-6324 CVE-2026-55761 GHSA-x626-fcwx-f5pc
  • GO-2026-6325 CVE-2026-27878 GHSA-6xff-cpcq-vpw2
  • GO-2026-6326 CVE-2026-55784 GHSA-334q-h5g3-fpxv
  • GO-2026-6327 CVE-2026-55874 GHSA-56wq-x3wv-3ff4
  • GO-2026-6328 CVE-2026-55785 GHSA-fp46-6vfw-gc9c
  • GO-2026-6329 CVE-2026-55873 GHSA-hgpf-8634-g44c
  • GO-2026-6330 CVE-2026-55764 GHSA-mrpp-v6pg-p54x
  • GO-2026-6333 CVE-2026-25712 GHSA-37w2-86g3-h4qh
  • GO-2026-6334 CVE-2026-24690 GHSA-47rq-xp99-92mx
  • GO-2026-6335 CVE-2026-27657 GHSA-4c8f-3m6h-m56r
  • GO-2026-6336 CVE-2026-26232 GHSA-5v69-g2m3-3hq3
  • GO-2026-6337 CVE-2026-28705 GHSA-7jvx-g65v-r899
  • GO-2026-6338 CVE-2026-22547 GHSA-922f-hfwp-p56f
  • GO-2026-6339 CVE-2026-20909 GHSA-fhq3-p242-2qpf
  • GO-2026-6340 CVE-2026-25718 GHSA-h697-89cp-24q8
  • GO-2026-6341 CVE-2026-26307 GHSA-h9c5-x7g8-4q7f
  • GO-2026-6342 CVE-2026-26247 GHSA-m5ch-ppfx-xv3v
  • GO-2026-6354 CVE-2026-78662
  • GO-2026-6355 CVE-2026-56855
  • Update to version 0.0.20260828T144745 2026-08-28T14:47:45Z.
  • GO-2026-6303 CVE-2026-56854
Record
SUSE-SU-2026:23712-1
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
github.com/seaweedfs/seaweedfs
Go
 before 0.0.0-20260612000715-b44cf51fe931
0.0.0-20260612000715-b44cf51fe931
seaweedfs
Bitnami
 before 4.34.0
4.34.0
govulncheck-vulndb
SUSE:Linux Enterprise Server 16.0
From an advisory covering 39 CVEs
 before 0.0.20260902T191204-160000.1.1
0.0.20260902T191204-160000.1.1
govulncheck-vulndb
SUSE:Linux Enterprise Server for SAP applications 16.0
From an advisory covering 39 CVEs
 before 0.0.20260902T191204-160000.1.1
0.0.20260902T191204-160000.1.1
govulncheck-vulndb
openSUSE:Leap 16.0
From an advisory covering 39 CVEs
 before 0.0.20260902T191204-160000.1.1
0.0.20260902T191204-160000.1.1

History

History
RecordedChangedSources
affected, facts
first indexedCVE List, EUVD, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2026-55874 is a high vulnerability (CVSS 7.7) in Seaweedfs, published July 8, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.61%, the 49th percentile. Fixed in github.com/seaweedfs/seaweedfs 0.0.0-20260612000715-b44cf51fe931.

References

Show 43 moreShow less
Pages All vulnerabilities Browse Docs Sources Guide Get API key
MoveEnter Open