Skip to main content
No exploitation reportedFix available

CVE-2026-55874

No exploitation reported by the sources we read.

  • Published2026-07-08
  • Fixed in4.34.0
  • WeaknessCWE-22

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-07-0815:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-30 09:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-55874?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-55874?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV
seaweedfs
BranchAffectedFixed in
4.34< 4.34.04.34.0
seaweedfs/seaweedfs
BranchAffectedFixed in
0.0< 0.0.0-20260612000715-b44cf51fe9310.0.0-20260612000715-b44cf51fe931

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-55874 Red Hat Product Security2 products fixed

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

  • RHSA-2026:68333 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat build of Cryostat security update

Full record on NVD

Fix

  1. Update seaweedfs to 4.34.0
  2. Vendor fix Red Hat Product Security RHSA-2026:68333 · 2 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2026:68333 · 20 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-07-08
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.17.7read 2026-10-23
  • CNAweakness (CWE)CWE-22read 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-10-29
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Published
2026-07-08
Last Modified
2026-07-08
NVD status
Deferred

Frequently asked questions

What is CVE-2026-55874?

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.

Is CVE-2026-55874 actively exploited?

Active exploitation of CVE-2026-55874 has not been confirmed. Its EPSS score was 0.6% on 2026-10-29, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-55874?

CVE-2026-55874 has a CVSS v3 base score of 7.7 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N.

Running seaweedfs? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database